View ID78K0_2073144.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

users manual target device 78k/0 series ID78K0 integrated debugger guide (windows? based operation) 1991 ? printed in japan document no. u11649ej1v2um00 (1st edition) date published march 1998 j cp(k) 1996

ibm pc/at is a trademark of international business machines corporation. i386 and i486 are trademarks of intel corporation. ms-dos and windows are either registered trademarks or trademarks of microsoft corporation in the united states and/or other countries. windows is an abbreviation of microsoft tm windows tm operating system. the information in this document is subject to change without notice. no part of this document may be copied or reproduced in any form or by any means without the prior written consent of nec corporation. nec corporation assumes no responsibility for any errors which may appear in this document. nec corporation does not assume any liability for infringement of patents, copyrights or other intellectual property rights of third parties by or arising from use of a device described herein or any other liability arising from use of such device. no license, either express, implied or otherwise, is granted under any patents, copyrights or other intellectual property rights of nec corporation or of others. m7a 96. 10
regional information some information contained in this document may vary from country to country. before using any nec product in your application, piease contact the nec office in your country to obtain a list of authorized representatives and distributors. they will verify: ? device availability ? ordering information ? product release schedule ? availability of related technical literature ? development environment specifications (for example, specifications for third-party tools and components, host computers, power plugs, ac supply voltages, and so forth) ? network requirements in addition, trademarks, registered trademarks, export restrictions, and other legal issues may also vary from country to country. nec electronics inc. (u.s.) santa clara, california tel: 408-588-6000 800-366-9782 fax: 408-588-6130 800-729-9288 nec electronics (germany) gmbh duesseldorf, germany tel: 0211-65 03 02 fax: 0211-65 03 490 nec electronics (uk) ltd. milton keynes, uk tel: 01908-691-133 fax: 01908-670-290 nec electronics italiana s.r.1. milano, italy tel: 02-66 75 41 fax: 02-66 75 42 99 nec electronics (germany) gmbh benelux office eindhoven, the netherlands tel: 040-2445845 fax: 040-2444580 nec electronics (france) s.a. velizy-villacoublay, france tel: 01-30-67 58 00 fax: 01-30-67 58 99 nec electronics (france) s.a. spain office madrid, spain tel: 01-504-2787 fax: 01-504-2860 nec electronics (germany) gmbh scandinavia office taeby, sweden tel: 08-63 80 820 fax: 08-63 80 388 nec electronics hong kong ltd. hong kong tel: 2886-9318 fax: 2886-9022/9044 nec electronics hong kong ltd. seoul branch seoul, korea tel: 02-528-0303 fax: 02-528-4411 nec electronics singapore pte. ltd. united square, singapore 1130 tel: 65-253-8311 fax: 65-250-3583 nec electronics taiwan ltd. taipei, taiwan tel: 02-719-2377 fax: 02-719-5951 nec do brasil s.a. cumbica-guarulhos-sp, brasil tel: 011-6465-6810 fax: 011-6465-6829 j98. 2
preface i preface thank you for purchasing the ID78K0 integrated debugger. conventional debuggers are used by entering commands directly. the ID78K0 integrated debugger, on the other hand, runs under windows to provide a friendly, easy-to-use gui (graphical u ser i nterface). its operation is mouse-based, and operation is possible without having to refer to the manual. also, frequently used commands are represented as buttons, allowing their activation simply by clicking the button with the mouse. ?purpose? the purpose of this manual is to provide the user with a brief explanation of how to use the ID78K0 integrated debugger. this manual should be read together with the ID78K0 integrated debugger users manual (reference). for a detailed explanation of each window, refer to the ID78K0 integrated debugger users manual (reference). ?files supplied with the integrated debugger? files used with the integrated debugger file name explanation ID78K0.exe debugger main section. the debugger is started by executing this file. ID78K0p.dll contains the libraries used for link processing with project manager. db78k0.dll contains libraries for file and symbol processing. as78k0.dll contains libraries for assembly and disassembly. ex78k0.dll contains libraries for communication with the in-circuit emulator. ex78k0.om0 downloaded into the in-circuit emulator when the debugger starts. ID78K0.hlp help file. expc.ini initial file. used to specify a set point and an interrupt address for the pc interface board. sample programs file name explanation sample.c sample program written in c. sub.c sample program written in c. contains the subroutines of sample.c. sample.lnk load module file for sample programs sample.c and sub.c. compiled by m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78014.
preface ii ?target device? the device which is to be the target of debugging by the integrated debugger is called a target device. the table below lists target devices, their associated device files, microprograms, and the names of the cpus which select the target devices. target device cpu name device file m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78014 78014 d014.78k m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78044 78044 d044.78k m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78054 78054 d054.78k m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78064 78064 d064.78k note: for details of other devices, contact your nec sales representative or authorized dealer. ?in-circuit emulator? an in-circuit emulator and dedicated interface board are required to use the integrated debugger. the table below lists the in-circuit emulator boards and interface boards that can be connected to host machines. in-circuit emulator product name explanation ie-78000-r-a in-circuit emulator main board ie-78xxx-r-em (note 1) product type dependent board note 1. for details, contact your nec sales representative or authorized dealer. interface boards product name explanation ie-70000-98-if-a interface board for pc-9801 and 9821 series (c bus) ie-70000-98-if-b interface board for pc-9801 and 9821 series (c bus) ie-70000-98n-if (note 2) interface board for 98note (110-pin expansion bus) ie-70000-pc-if-b (note 3) interface board for ibm-pc/at series (isa bus) note 2. the ie-70000-98n-if is corrected to the expansion bus (110-pin type) of 98note. note 3. the ie-70000-pc-if-a cannot be used.
preface iii ?host machine? the integrated debugger runs under windows. the table below lists the requirements for the machine to be used. item requirement host machine pc-9801, 9821 or ibm-pc/at series cpu i80386 or above (i80486, 33 mhz or above recommended) main memory 4m bytes or more (8m bytes or more recommended) os windows 3.1 or windows 95 screen size 640 x 400 dots or larger (800 x 600 dots or larger recommended) ?configuration? chapter 1 overview explains general operations of the integrated debugger. chapter 2 basic operations explains the relationships between windows and other information by purpose. chapter 3 advanced use of ID78K0 describes the terms used in the explanation of the integrated debugger. ?conventions? the following explains the conventions used throughout this manual. : indicates a key to be pressed. + : indicates keys which must be pressed at the same time. : indicates a character string. : indicates a character. [ ] : indicates an optional parameter. grph key : representation of a key featured by the pc-9801 and 9821 series. the alt key of the ibm-pc/at series has the same function. all representations of keys in this manual are for the pc-9801 and 9821 series. when using an ibm- pc/at series computer as a host machine, see appendix b .
preface iv ?screen? the descriptions in this manual refer to windows 95 screens unless specified otherwise. the differences between windows 3.1 screens and windows 95 screens are as described below. windows 3.1 windows 95 remarks control menu box displays the control menu. with windows 95, an icon or the windows logo is displayed. minimizes the window. maximizes the window. window size modification restores the window to its original size. close button (none) closes the window. multiple options can be selected. option only one of the multiple options can be selected. windows 95 screen windows 3.1 screen control menu box window size modification, program closing options
preface v ?cautions? to perform source debugging, add options for creating debug information whenever compiling, assembly, or linking is performed. otherwise, source debugging may not be possible. when creating your own startup routine in c, add the symbols given below. failing to do so may result in part of the step execution not being performed correctly. where to add symbol to be added start of startup routine _@cstart end of startup routine _@cend ?related documents? the documents (users manuals) related to this manual are listed below: document number document name japanese english ID78K0 integrated debugger users manual, reference u11539j u11539e language eeu-815 eeu-1399 ra78k series assembler package operation eeu-809 eeu-1404 ra78k series structured assembler preprocessor eeu-817 eeu-1402 language eeu-655 eeu-1280 cc78k series c compiler operation eeu-656 eeu-1284 78k/0 series users manual, instructions ieu-849 eeu-1372 m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd78014, 78014y sub-series u-10085jj eeu-1343 note: the above documents may be revised without notice. use the latest versions when designing an application system.
contents vi chapter 1 overview------------------------------------------------------------------------------------------------ 1 1.1 starting and terminating the debugger ------------------------------------------------------- 2 1.1.1 starting ----------------------------------------------------------------------------------- 2 1.1.2 terminating------------------------------------------------------------------------------ 3 1.2 making maximum use of the main window -------------------------------------------------- 4 1.2.1 main window functions -------------------------------------------------------------- 4 1.2.2 making maximum use of menus --------------------------------------------------- 5 1.2.3 one-touch tool bar operation----------------------------------------------------- 5 1.2.4 using information provided by the status bar ---------------------------------- 7 chapter 2 basic operations ------------------------------------------------------------------------------------- 8 2.1 establishing the environment -------------------------------------------------------------------- 9 2.1.1 selecting a device--------------------------------------------------------------------- 10 2.1.2 selecting a cpu clock --------------------------------------------------------------- 11 2.1.3 mapping ---------------------------------------------------------------------------------- 12 2.1.4 specifying a stack area-------------------------------------------------------------- 13 2.1.5 setting the alternate software operation clock -------------------------------- 14 2.1.6 setting memory banks --------------------------------------------------------------- 16 2.1.7 loading/saving the debugging environment ----------------------------------- 18 2.2 source level debugging -------------------------------------------------------------------------- 20 2.2.1 notes on compilation, assembly, and linking---------------------------------- 20 2.2.2 downloading a program-------------------------------------------------------------- 21 2.2.3 displaying a source ------------------------------------------------------------------- 22 2.2.4 functions supported by the source window ----------------------------------- 23 2.2.5 jump from the source window----------------------------------------------------- 24 2.3 instruction level debugging---------------------------------------------------------------------- 25 2.3.1 assembly language display and online assembly --------------------------- 26 2.3.2 saving and referencing displayed assembly language code ------------ 27 2.3.3 functions supported by the assemble window -------------------------------- 28 2.3.4 jump from the assemble window ------------------------------------------------- 29 2.4 manipulating memory ------------------------------------------------------------------------------ 30 2.4.1 displaying and modifying memory data------------------------------------------ 30 2.4.2 basic memory data operations ---------------------------------------------------- 31 2.4.3 saving and referencing displayed memory data ----------------------------- 32 2.4.4 functions available in the memory window------------------------------------- 33 2.4.5 jumping from the memory window------------------------------------------------ 34 2.5 manipulating registers ---------------------------------------------------------------------------- 35 2.5.1 displaying and modifying registers ----------------------------------------------- 35 2.5.2 saving and referencing displayed register data ----------------------------- 36 2.5.3 functions available in the register window ------------------------------------ 37 2.5.4 functions available in the sfr window ----------------------------------------- 37 2.5.5 jumping from the register window ----------------------------------------------- 38 2.6 creating events ------------------------------------------------------------------------------------- 39 2.6.1 setting and referencing events in the source window and assemble window --------------------------------------------------------------- 40 2.6.2 creating event conditions ----------------------------------------------------------- 41 2.6.3 setting events -------------------------------------------------------------------------- 43 2.6.4 saving and restoring event conditions------------------------------------------ 44 2.6.5 functions available in the event manager--------------------------------------- 45 2.6.6 jumping to an event setting address--------------------------------------------- 46
contents vii 2.7 manipulating symbols (variables) -------------------------------------------------------------- 47 2.7.1 displaying and modifying variables ----------------------------------------------- 48 2.7.2 saving and referencing symbol data -------------------------------------------- 50 2.7.3 functions available in the variable window and local variable window --------------------------------------------------------------- 51 2.8 using the tracer effectively ---------------------------------------------------------------------- 52 2.8.1 displaying trace results ------------------------------------------------------------ 53 2.8.2 saving and referencing trace results------------------------------------------- 54 2.8.3 effective trace memory usage 1 (trace mode setting) --------------------- 55 2.8.4 effective trace memory usage 2 (trace full break, snapshot trace)----------------------------------------------- 59 2.8.5 inter-window connection functions (window connection function, jump function) ------------------------------- 61 2.9 measuring the execution time ------------------------------------------------------------------ 63 2.9.1 measuring program execution time ---------------------------------------------- 63 2.9.2 time measurement using the tracer --------------------------------------------- 64 chapter 3 advanced use of ID78K0 ----------------------------------------------------------------------------- 65 3.1 verifying the validity of evaluation-------------------------------------------------------------- 66 3.1.1 coverage -------------------------------------------------------------------------------- 66 3.1.2 verifying the validity of evaluation based on coverage---------------------- 67 3.1.3 notes on coverage results --------------------------------------------------------- 69 3.2 using external sense clips ---------------------------------------------------------------------- 70 3.2.1 tracing external data----------------------------------------------------------------- 71 3.2.2 trigger output -------------------------------------------------------------------------- 72 3.2.3 real-time ram output -------------------------------------------------------------- 73 3.2.4 creating an event by anding a data condition-------------------------------- 74 3.3 measuring time by setting conditions -------------------------------------------------------- 75 appendix a error messages ------------------------------------------------------------------------------------- 77 appendix b key functions --------------------------------------------------------------------------------------- 87 b.1 functions of special function keys------------------------------------------------------------ 87 b.2 functions of special function keys ( ctrl + key) ---------------------------------------- 88 appendix c menus------------------------------------------------------------------------------------------------- 89
[memo]
chapter 1 overview 1 chapter 1 overview this chapter outlines the debugger. 1.1 starting and terminating the debugger this section explains how to start and terminate the debugger. 1.2 making maximum use of the main window the main window appears when the debugger is started. the main window supports many functions. by making full use of these functions, the efficiency of debugging can be significantly enhanced.
chapter 1 overview 1.1 starting and terminating the debugger 2 1.1 starting and terminating the debugger the debugger can be started and terminated easily. to start the debugger, select the icon, shortcut key, or corresponding item in the start menu. these will have been registered when the software was installed. to terminate the debugger, select the corresponding item from the menu. when terminating the debugger, you may select saving of the debugging environment. doing so allows the debugger to be used immediately the next time it is started. 1.1.1 starting 1. start windows. 2. turn on the in-circuit emulator. 3. turn on the target, if being used. 4. double-click the icon or shortcut key, registered when the debugger was installed. 5. after the debugger starts, the configuration dialog box appears.
chapter 1 overview 1.1 starting and terminating the debugger 3 6. select a debug target device. (note that the debug target device can be selected only when the debugger is being started.) 7. set the clock source, memory mapping, and other required items. 8. once all the necessary items have been set, click the button. this completes device initialization and causes the required data to be downloaded to the in-circuit emulator. 9. once downloading has been completed, the main window of the debugger opens. the main window is used as the core window for debugging. 1.1.2 terminating 1. select file from the menu bar of the main window. 2. select exit from the f ile pull-down menu. 3. the exit debugger dialog box appears. 4. click the button to terminate the debugger.
chapter 1 overview 1.2 making maximum use of the main window 4 1.2 making maximum use of the main window all debugger windows are based on the main window. the main window supports many functions, all of which are easy to use. 1.2.1 main window functions the main window supports four major functions. many debugger operations are performed from the main window. remember the following four functions. function description menu bar contains all the functions supported by the debugger. to perform some operation with the debugger, first check the contents of the menu bar. tool bar contains the most-frequently used commands. while no target is connected, try clicking each of the buttons, and make a note of the graphic identifying each button. window display area windows are displayed in this area. these windows include, for example, the source window and assemble window, both of which are used whenever debugging is performed. status bar the status of the in-circuit emulator (ie) is displayed in this area. the ie status and break cause are particularly important. menu bar: all operations supported by the debugger are displayed on pull-down menus. tool bar: contains he most-frequently used commands. tool bar commands can be executed by a single action, making them extremely conventient to use. window display area: windows are displayed. status bar: information such as ie inforation is displayed.
chapter 1 overview 1.2 making maximum use of the main window 5 1.2.2 making maximum use of menus the menus contain all the functions supported by the debugger. even when you are not familiar with the debugger's functions, briefly studying each of the pull- down menus will allow you to understand the range of functions available. the menus are outlined below. menu description file contains file operation commands. this menu enables the switching of the source displayed in the source window, the loading and saving of project files, and other file operations. edit provides commands for copying and pasting displayed data, as well as commands for memory editing. view contains display commands. using this menu, you can retrieve variables, enter the display start address, and display variables. option allows you to display and hide the tool bar, status bar, and buttons in each window, and to establish the debugger environment. execute contains execution commands. also, trace mode setting is performed from this menu. operation allows you to perform window mode switching, and to specify connection to the trace window. browse contains the commands used to open each window. from this menu, you can display windows such as the event and coverage windows. jump allows you to jump to the source window, assemble window, and memory window. window allows you to specify how windows are to be displayed, the arrangement of icons, and also enables switching between windows. help displays help information. 1.2.3 one-touch tool bar operation the tool bar consists of buttons which correspond to frequently used commands. commands are executed simply by clicking the corresponding button. the function of each button is identified by a suitably representative graphic. the commands assigned to the tool bar buttons can also be executed from the menu bar. commands for program execution: commands for controlling program execution window manipulation commands: frequently used commands such as that for displaying a source and that for displaying registers.
chapter 1 overview 1.2 making maximum use of the main window 6 display description stops user program execution. executes a user program. as soon as the break conditions are satisfied, the user program terminates. executes a user program. even when break conditions are satisfied, the user program does not terminate. executes the program in real time, until execution returns to the calling function. executes the program, step by step. every time this button is clicked, one step of the program is executed. for source level debugging, one step corresponds to one line. for instruction level debugging, one step corresponds to one instruction. performs next step execution of the program. every time this button is clicked, one step of the program is executed, by means of next step execution. for source level debugging, one step corresponds to one line. for instruction level debugging, one step corresponds to one instruction. initializes the debugger or emulation cpu. opens the reset debugger dialog box. displays the source text. opens the source window. displays the stack contents. opens the stack window. displays a disassembled program. opens the assemble window. displays the contents of memory. opens the memory window. displays the register contents. opens the register window. registers and sets break events. opens the break dialog box. displays trace results. opens the trace view window. registers and sets trace events. opens the trace dialog box. displays the sfr contents. opens the sfr window. displays timer measurement results. opens the timer window.
chapter 1 overview 1.2 making maximum use of the main window 7 1.2.4 using information provided by the status bar the status bar displays important data including, for example, the status of the ie and the cause of a break. if a break occurs at a point where no break has been set, or if no source appears when a break occurs, for example, check this area first. status bar: information relating to ie is displayed. break cause information is particularly important. 1. source file name: displays the source file name and source line number corresponding to the indicated pc value. if no file information is available, "---" is displayed. 2. function name: displays the function name corresponding to the indicated pc value. if no function information is available, "---" is displayed. 3. pc value: displays the current pc value. 4. cpu status: displays the status of the cpu ( m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m m pd780xx: target device). cpu status description target the target is on. hold bus hold mode standby halt or stop mode lutchup latch-up has been detected. turn off the target and in-circuit emulator immediately. 5. ie status: displays the operation status of the in-circuit emulator. ie status description run real-time execution in progress step step-by-step execution in progress break break status trace tracing in progress timer timer measurement in progress 6. break cause: displays the reason for a break. the table below lists possible break causes. cause description compulsory break normal break (manual break) temporally break normal break (break caused by internal processing) event break break triggered by an event out of range break break caused by procedure step termination trace full break break caused by trace full state non map break access to a non-mapped area was attempted. sfr illegal illegal access to an sfr was attempted. stack overflow break caused by stack overflow write protect an attempt was made to write to a write-protected area.
chapter 2 basic operations 8 chapter 2 basic operations this chapter explains the basic operations of the ID78K0. each section clarifies how windows are related to each other. 2.1 establishing the environment explains how to establish a debugging environment. 2.2 source level debugging explains the use of the source window to debug a source program. 2.3 instruction level debugging explains the use of the assemble window to perform assembler level debugging. 2.4 manipulating memory explains the use of the memory window to perform modification, initialization, and other operations on memory. 2.5 manipulating registers explains the functions of the register window, used to manipulate general-purpose registers, and those of the sfr window, used to manipulate sfrs. 2.6 creating events events are very useful for debugging. events can be used for program and trace control. this section explains how to set an event. 2.7 manipulating symbols (variables) the debugger supports the input of symbols as data. this section explains how to enter symbols and display variables. 2.8 using the tracer effectively the ie-78000-r-a contains 32k frames of trace memory. the tracer is used to trace data, making it very useful for detecting program problems. this section explains the use of the tracer. 2.9 measuring the execution time explains the time required to execute a program from beginning to end, and time tags written in the tracer.
chapter 2 basic operations 2.1 establishing the environment 9 2.1 establishing the environment establishing an environment allows the debugger to recognize the configuration of a target system. establishing a debugging environment enables the maximum utilization of the debugger functions. the environment must be established whenever the debugger is started. once an environment has been established, it can be saved to a file, subsequently eliminating the need to newly establish the environment. when the debugger is next started, the environment can be established simply by loading the file (project file). for the ID78K0 operating environment, set the following items: item setting window location in environment setup diagram remarks device <1> cpu cpu clock <2> <3> <4> <6> <7> clock peripheral equipment operation configuration dialog box <1> cpu memory bank switching configuration dialog box bank set dialog box <1> cpu <8> memory alternate operation clock configuration dialog box <1> cpu can be set only when the debugger is being started memory mapping configuration dialog box <5> <8> memory mask option mask option dialog box <1> cpu can be set at any time cpu <1> ie alternate memory (64k bytes) <5> memory <8> external clock subsystem clock clock <6> <7> power supply ep-78xxx-r in-circuit emulator target jig target jig internal clock external clock or 6-8pin short clock <2> <3> subsystem clock or 6-8pin short <4> memory ie-78000-r-a in circuit emulator establishing an environment
chapter 2 basic operations 2.1 establishing the environment 10 2.1.1 selecting a device a device can be selected in the configuration dialog box that appears when the debugger is started. note that once the debugger has started, this selection cannot be changed. setting in the configuration dialog box: 1. start the debugger. 2. select a device in the configuration dialog box that appears when the debugger is started. when the main window has already been opened: 1. terminate, then restart, the debugger. selecting a device
chapter 2 basic operations 2.1 establishing the environment 11 2.1.2 selecting a cpu clock a cpu clock is selected in the configuration dialog box that appears when the debugger is started. note that once the debugger has started, the cpu clock cannot be changed. setting in the configuration dialog box : 1. start the debugger. 2. change the cpu clock in the configuration dialog box that appears when the debugger is started. when the main window has already been opened: 1. terminate, then restart, the debugger. when "internal" is selected as the cpu clock, the clock provided by the in-circuit emulator is used as the cpu clock. this clock frequency is determined by the connected emulation board (em board). emulation board(note) cpu clock frequency when "internal" is selected ie-78014-r-em ie-78014-r-em-a 8.38 mhz ie-780208-r-em ie-78044-r-em 4.19 mhz ie-78064-r-em ie-78078-r-em 5.0 mhz ie-78098-r-em 6.0 mhz note for emulation boards not listed here, refer to the manual provided with the board. to use the clock provided by the target, select "external."
chapter 2 basic operations 2.1 establishing the environment 12 2.1.3 mapping when external rom/ram is used in addition to internal rom and internal ram (including sfrs and registers), the area to be mapped must be set. to add an area to be mapped: 1. open the configuration dialog box. this dialog box appears when the debugger is started. it can also be displayed by selecting option -> c onfiguration... from the menu bar. 2. set the memory attribute area, then click the button. to delete a mapped area: 1. open the configuration dialog box. this dialog box appears when the debugger is started. it can also be displayed by selecting option -> c onfiguration... from the menu bar. 2. select the mapped area to be deleted, then click the button. mapping can be performed using the configuration dialog box. emulation rom: ie alternate rom emulation ram: ie alternate ram target : target ram stack : stack area specification
chapter 2 basic operations 2.1 establishing the environment 13 2.1.4 specifying a stack area to monitor stack operation, specify a stack area. when a stack area has been specified, any stack operation (call, ret, push, pop) performed outside the set area is detected as being an illegal access. an area in internal high-speed ram can be specified as the stack area. when no stack area is specified, the entire internal high-speed ram area is used as the stack area. to specify a stack area: 1. open the configuration dialog box. this dialog box appears when the debugger is started. it can also be displayed by selecting option -> c onfiguration... from the menu bar. 2. set the memory attribute area, then click the button. to cancel the stack area specification: 1. open the configuration dialog box. this dialog box appears when the debugger is started. it can also be displayed by selecting option -> c onfiguration... from the menu bar. 2. select the mapped stack area to be deleted, then click the button. the pd78014 contains 1024 bytes of internal high-speed ram between addresses 0xfb00 and 0xfeff. therefore, set the area to be mapped within this range. m
chapter 2 basic operations 2.1 establishing the environment 14 2.1.5 setting the alternate software operation clock the alternate software is control software that runs on the 78k0 device. it controls the resources (register values, sfrs, and memory) of the target while the in-circuit emulator is in break mode. the alternate software accesses the target resources directly. the operation of the alternate software uses the same clock as the user program. if, therefore, the user program uses a low-speed clock while the in-circuit emulator is in break mode, the alternate software will also operate slowly, thus lowering the overall speed of debugger operation. to avoid this, specify the use of the alternate software operation clock. to set the operation clock: 1. open the configuration dialog box. this dialog box appears when the debugger is started. it can also be displayed by selecting option -> c onfiguration... from the menu bar. 2. select the operation clock in the alternate software operation clock selection area. setting alternate software operation clock
chapter 2 basic operations 2.1 establishing the environment 15 the alternate software operating environment is illustrated below. ex78k0.0m0 sv board cpu for ie control: v53 during break: alternate software while running: user program emulation cpu: 78k0 ie-78000-r-a in circuit emulator bk, em board i/o and memory on the target power supply target ID78K0.exe as78k0.dll db78k0.dll ex78k0.dll trace board control software
chapter 2 basic operations 2.1 establishing the environment 16 2.1.6 setting memory banks the 78k0 series has an address space consisting of up to 64k bytes between addresses 0 and 0xffff. a program of 64k bytes or more can be run by switching part or all of the program area between addresses 0 and 0xffff. the structure of the memory banks is shown below. in the following figure, the 16k-byte space between addresses 4000h and 7fffh is used for the memory banks. five banks, 0 to 4, are used. when bank 0 is selected, data in bank 0 can be accessed at addresses 4000h to 7fffh, a linear space existing between address 0h and 7fffh. when bank 0 is selected, the spaces corresponding to banks 1 to 4 cannot be accessed. when bank 3 is selected, the data in bank 3 can be accessed between addresses 4000h and 7fffh. the other banks cannot be accessed. memory bank switching 0000h ffffh sfr 3fffh 4000h 7fffh internal rom bank1 bank2 bank3 bank4 0000h ffffh sfr 3fffh 4000h 7fffh internal rom bank0 bank1 bank2 bank4 when bank 0 is selected when bank 3 is selected bank memory bank0 bank memory bank3
chapter 2 basic operations 2.1 establishing the environment 17 to switch between memory banks, program the generation of the upper address by using, for example, ports. so that the debugger can control the memory banks effectively, set the ports and other data to be used for bank switching when establishing the environment. to set up the memory banks, click the bank set button in the configuration dialog box. the dialog box for memory bank setting will appear.
chapter 2 basic operations 2.1 establishing the environment 18 2.1.7 loading/saving the debugging environment saving the debugging environment into a project file enables subsequent debugging to be performed in exactly the same environment. debugging environment method at start specify a project file to be read, using its full path name, as a start option. load after start load a project file by using the project file load dialog box. after start save a project file using the project file save dialog box. save at exit select "save project file" in the exit debugger dialog box, then terminate the debugger. enter the full path name of a project file. after the debugger starts (loading) before the debugger starts when the debugger terminates after the debugger starts (save) when terminating the debugger, select \ \
chapter 2 basic operations 2.1 establishing the environment 19 data to be loaded/saved window data configuration dialog box all items bank set dialog box all items main window setting information load module dialog box file information downloaded extended option dialog box setting information mask option dialog box setting information source path dialog box source path information source window window display information, font information assemble window window display information, display start address memory window window display information, display start address stack window window display information sfr window window display information local variable window window display information trace view window window display information show trace dialog box setting information snap trace dialog box setting information event manager window display information, all event information event link dialog box window display information break dialog box window display information trace dialog box window display information snap-shot dialog box window display information event set dialog box window display information register window window display information, displayed bank variable window window display information, displayed variable information coverage window window display information
chapter 2 basic operations 2.2 source level debugging 20 2.2 source level debugging ID78K0 can set breakpoints and display variables for a source. many source level operations are supported, thus greatly enhancing debugging efficiency. source level debugging can be performed by loading a file containing source information. source level debugging is particularly effective for debugging programs written in c or structured assembly language. 2.2.1 notes on compilation, assembly, and linking when source level debugging is performed, the file to be loaded must contain source debugging information. source debugging information is included in the object by specifying the option for adding debugging information at assembly or compile time. the following shows how to set options at compilation, assembly, and linking: type of source to be debugged required action without in-line assembly description specify the -g option at compile time. c program with in-line assembly description 1. at compile time, specify the -a option to output an assembly source file. 2. assemble the source generated in 1, above, without specifying any debug options (-ga, - nga). structured assembly language program 1. specify the -gs option at structured assembly. 2. assemble the source generated in 1, above, without specifying any debug options (-ga, - nga). assembly language program specify the -ga option at assembly. link specify the -g option at linking.
chapter 2 basic operations 2.2 source level debugging 21 2.2.2 downloading a program load module files and hexadecimal files can be downloaded. when a downloaded file contains source debugging information, source level debugging can be performed. to perform downloading: 1. select file -> download... from the menu bar to open the load module dialog box. 2. load the desired file. select the file to be loaded. \
chapter 2 basic operations 2.2 source level debugging 22 2.2.3 displaying a source after a load module file containing source debugging information has been downloaded, the source can be displayed. if the source file is stored in a directory other than that containing load module file, or if the source file is stored in more than one directory, source path information must be provided to the debugger. to display a source: 1. select browse -> s ource text... from the menu bar or click the button to open the source window. to change the source file displayed in the source window: 1. activate the source window. 2. select file -> o pen... from the menu bar to open the source file select dialog box. when a source file is stored in another directory or in more than one directory: 1. select option -> source p ath... from the menu bar to open the source path dialog box. specifying a directory containing a source file: source path dialog box displaying a source file: source window selecting a source file to be displayed in the source window: source file select dialog box \
chapter 2 basic operations 2.2 source level debugging 23 2.2.4 functions supported by the source window the source window supports a wide range of functions, such as the setting of breakpoints and the addition of variables to be displayed. the supported functions are listed below: procedure function using the mouse from the keyboard setting/deleting a breakpoint click the point mark area. 1. select a line number (with the mouse). 2. select execute -> set b p from the menu bar. ( ctrl +b ) setting pc --- 1. select a line number (with the mouse). 2. select execute -> se t pc from the menu bar. ( ctrl +e ) displaying a variable 1. select a variable. 2. click the button then the button. 1. select a variable (with the mouse). 2. select view -> w atch variable... or v iew variable... from the menu bar. retrieving a character string 1. select a variable. 2. click the button. 1. select a variable (with the mouse). 2. select view -> s earch... from the menu bar. checking an event 1. select an event line. 2. click the button. 1. select an event line (with the mouse). 2. select view -> e vent? from the menu bar. setting, deleting, and displaying a breakpoint, and displaying an event select a character string. (token-based selection is enabled by double-clicking.) select an event setting line. search button: find dialog box view button: variable view dialog box watch button: variable window event? button: event manager pc position line number: mainly used as the pointer for keyboard entry.
chapter 2 basic operations 2.2 source level debugging 24 2.2.5 jump from the source window jump from the source window to the assemble window and memory window is supported. using the jump function, it is easy to check the source text assemble results. select a source line number as the jump destination. then, the start address of the selected source line is set as the jump pointer. jump destination procedure assemble window 1. select a source line number. 2. select jump -> a ssemble... from the menu bar. memory window 1. select a source line number. 2. select jump -> m emory... from the menu bar. the jump destination is the address of the source line, displayed in reverse video: in the following example, the start address of the 38th line is set as the jump pointer. jump to the assemble window jump to the memory window
chapter 2 basic operations 2.3 instruction level debugging 25 2.3 instruction level debugging the contents of memory can be displayed, modified, and retrieved in assembly language. instruction level debugging supports a higher level of precision than source level debugging. assembly language code can be displayed in the assemble window and trace view window. this section mainly explains the operations supported by the assemble window.
chapter 2 basic operations 2.3 instruction level debugging 26 2.3.1 assembly language display and online assembly the assemble window allows you to view assembly language code and perform online assembly. with the online assemble function, patching can be performed. simple bugs can be corrected and confirmed immediately. assemble procedure to select a displayed address open the addressing dialog box in either of the following two ways: 1. select browse -> a ssemble... from the menu bar. 2. click the button. display to display instructions starting from an address selected in another window (such as the source, memory, or register window) 1. select an address to be used as the display pointer. 2. select jump -> a ssemble... from the menu bar. modification 1. open the assemble window. 2. click the button to enter modify mode. 3. position the cursor to the mnemonic display/modification area, then correct the program. 4. after completing the correction of the program, click the, button to rewrite the program. 5. click the button to enter view mode. specifying the start address for display: addressing dialog box assembly language display: assemble window (display mode) tomodify button: change to modify mode toview button: change to view mode online assembly program correction: assemble window (modify mode)
chapter 2 basic operations 2.3 instruction level debugging 27 2.3.2 saving and referencing displayed assembly language code the displayed assembly language code can be saved to a file. the saved file can subsequently be referenced. the file is saved in text format, such that any commercially available editor can be used to view its contents. to save displayed assembly language code to a file: 1. activate the assemble window. 2. select file -> save a s... from the menu bar. 3. save the displayed assembly language code using the view file save dialog box. to open and reference the saved file: 1. activate the assemble window. 2. select file -> o pen... from the menu bar. 3. load the file to be referenced using the view file load dialog box. saving the display contents to a file: view file save dialog box reference window the window used for loading and opening a file is opened as a reference window. all operations other than search are disabled while this window is displayed. displaying the contents saved to a file: view file load dialog box \ \
chapter 2 basic operations 2.3 instruction level debugging 28 2.3.3 functions supported by the assemble window the assemble window supports many functions such as the setting of breakpoints and pc setting. the supported functions are listed below: procedure function using the mouse using the keyboard setting/deleting a breakpoint click the point mark area. 1. select an address (with the mouse). 2. select execute -> set b p from the menu bar. ( ctrl +b ) setting pc --- 1. select an address (with the mouse). 2. select execute -> se t pc from the menu bar. ( ctrl +e ) retrieving a character string 1. select a character string. 2. click the button. 1. select a character string (with the mouse). 2. select view -> s earch... from the menu bar. checking an event 1. select the address at which an event is set. 2. click the button. 1. select the address at which an event is set (with the mouse). 2. select view -> e vent? from the menu bar. event? button: event manager search button: find dialog box tomodify button: program correction address: the address displayed in reverse video is set as the pointer for a function. pc position setting, deleting, and displaying a breakpoint, and displaying an event
chapter 2 basic operations 2.3 instruction level debugging 29 2.3.4 jump from the assemble window jump from a line in the assemble window to the corresponding source line or memory address is supported. select an address as the jump destination. then, the selected address is set as the jump pointer. when the jump destination is the source window, a jump is made to a source line including the jump pointer. jump destination procedure source window 1. select an address. 2. select jump -> s ource text... from the menu bar. memory window 1. select an address. 2. select jump -> m emory... from the menu bar. the jump destination is the address displayed in reverse video: in the followin g example, address 132h is the jump pointer. jump to the source window a jump is made to the source line including address 132h in the source window. jump to the memory window
chapter 2 basic operations 2.4 manipulating memory 30 2.4 manipulating memory the user can display, modify, and search for memory data. the user can display and modify memory data in ascii format. 2.4.1 displaying and modifying memory data the user can display and modify memory data in the memory window. memory procedure when a display address is to be selected the addressing dialog box can be opened by means of either of the following two procedures: 1. select browse -> m emory... from the menu bar. 2. select the button. display when memory data is to be displayed starting from an address selected in another window (such as the source window, assemble window, or register window) 1. select an address to act as a display pointer. 2. select jump -> m emory... from the menu bar, or press ctrl + m. modification 1. open the memory window. 2. switch to modify mode by clicking the button. 3. position the cursor to the desired memory display/modification area, then modify the data. 4. after entering the new data, execute the modification by clicking the button. 5. switch to view mode by clicking the button. specifying a desired display start address: addressing dialog box memory display: memory window (view mode) memory modification: memory window (modify mode) tomodify button: used to switch to modify mode. toview button: used to switch to view mode.
chapter 2 basic operations 2.4 manipulating memory 31 2.4.2 basic memory data operations basic memory data operations are enabled by activating the memory window. the basic operations include initialization, copy, and comparison. to initialize memory: select edit -> m emory -> memory f ill... from the menu bar. to copy memory data: select edit -> m emory -> memory c opy... from the menu bar. to compare memory data: select edit -> m emory -> memory comp are... from the menu bar. memory initialization: memory fill dialog box string data of no more than 16 bytes can be specified. activate the memory window. memory copy: memory copy dialog box a memory copy destination can be specified. memory comparison: memory compare dialog box if memory data comparison reveals a mismatch, the memory compare result dialog box appears.
chapter 2 basic operations 2.4 manipulating memory 32 2.4.3 saving and referencing displayed memory data displayed memory data can be saved to a file. a file containing saved memory data can be referenced. memory data is saved in text format, allowing an editor to be used to reference saved memory data. to save displayed memory data to a file: 1. activate the memory window. 2. select file -> save a s... from the menu bar. 3. save the displayed memory data by using the view file save dialog box. to open and reference a file containing saved memory data: 1. activate the memory window. 2. select file -> o pen... from the menu bar. 3. load the file to be referenced by using the view file load dialog box. saving displayed memory data to a file: view file save dialog box reference window. load and open the file to be displayed. the window is opened for reference. all operations other than search are disabled. displaying memory data that has been saved to a file: view file load dialog box \ \
chapter 2 basic operations 2.4 manipulating memory 33 2.4.4 functions available in the memory window the memory window allows the user to perform a range of functions including modification in ascii format, and data search. the available functions are listed below. function procedure character string search 1. select a character string. 2. click the button, or select view -> s earch... from the menu bar. ascii character display selection select view -> m emory -> a scii from the menu bar. type display selection select view -> m emory -> n ibble, b yte, w ord, or l ong from the menu bar. number system display selection select view -> b in, o ct, d ec, or h ex from the menu bar. search button: find dialog box address display: an address displayed in reverse video acts as a pointer to be used with each function. data display. tomodify button: used to modify data. the user can select binary, octal, decimal, or hexadecimal display. the user can also select nibble, byte, word, and long for display. display in ascii
chapter 2 basic operations 2.4 manipulating memory 34 2.4.5 jumping from the memory window this function enables a jump to the source line or disassembly start address corresponding to an address in the memory window. a jump destination can be specified by selecting a desired address. the selected address serves as a jump pointer. when a jump is made to the source window, a jump to the source line including the jump pointer occurs. jump destination procedure source window 1. select an address. 2. select jump -> s ourcetext... from the menu bar. assemble window 1. select an address. 2. select jump -> a ssemble... from the menu bar. a jump is made to the address displayed in reverse video. in this case, address d0h is the jump pointer. jump to the source window. a jump to the source line including address d0h in the source window occurs. jump to the assemble window
chapter 2 basic operations 2.5 manipulating registers 35 2.5 manipulating registers registers are classified into three major types: control registers, general-purpose registers, and special function registers (sfrs). the control registers and general-purpose registers can be displayed and modified in the register window. the sfrs can be displayed and modified in the sfr window. 2.5.1 displaying and modifying registers the user can display and modify control registers, general-purpose registers, and sfrs. the user can manipulate control registers and general-purpose registers in the register window, and manipulate sfrs in the sfr window. memory procedure control registers and general- purpose registers (register window) select browse -> r egister... from the menu bar, or click the button. display sfrs (sfr window) select browse -> sf r... from the menu bar, or click the button. modification (common to the register window and sfr window) 1. open a desired window. 2. switch to modify mode by clicking the button. 3. position the cursor to a desired register, then modify the data. 4. after making the modification, execute the modification by clicking the button. 5. switch to view mode by clicking the button. register window (view mode) register window (modify mode) tomodify button: used to switch to modify mode. toview: used to switch to view mode. sfr window (view mode) sfr window (modify mode) displaying and modifying control registers and general-purpose registers displaying and modifying sfrs
chapter 2 basic operations 2.5 manipulating registers 36 2.5.2 saving and referencing displayed register data displayed register data can be saved to a file. a file containing saved register data can be referenced. register data is saved in text format, allowing an editor to be used to reference saved register data. to save displayed register data to a file: 1. activate a desired window. 2. when the register window has been selected, select file -> o pen/save condition -> sa ve file as... from the menu bar. when the sfr window has been selected, select file -> save a s... from the menu bar. 3. save the displayed register data by using the view file save dialog box. to open and reference a file containing saved register data: 1. activate a desired window. 2. when the register window has been selected, select file -> o pen/save condition -> o pen condition... from the menu bar. when the sfr window has been selected, select file -> o pen... from the menu bar. 3. load the file to be referenced by using the view file load dialog box. saving displayed register data to a file: view file save dialog box reference window. load and open the file to be displayed. the window is opened for reference. all operations related to modification are disabled. displaying register data that has been saved to a file: view file load dialog box \ \
chapter 2 basic operations 2.5 manipulating registers 37 2.5.3 functions available in the register window the register window allows the user to choose between the function name display option and absolute name display option, choose between the register display option and pair register display option, and so forth. the available functions are listed below. function procedure absolute name display/function name display absolute name: select view -> a bsolute name from the menu bar. function name: select view -> f unction name from the menu bar. di splay switching register display/pair register display register display: select view -> r egister from the menu bar. pair register display: select view -> register p air from the menu bar. number system display selection select view -> b in, o ct, d ec, or h ex from the menu bar. 2.5.4 functions available in the sfr window the sfr window allows the user to select the display order, specify whether attribute data is to be displayed, and so forth. the available functions are listed below. function procedure display order selection the user can choose either address order or alphabetic order as the display order: select view -> sf r -> a ddress sort from the menu bar. attribute display selection select view -> sf r -> at tribute -> s how or hi de from the menu bar. pickup display selection only those sfrs that have been modified but not yet written to a target in modify mode are displayed. select view -> sf r -> p ick up from the menu bar. address order, attribute display (default) pickup display hiding attribute data alphabetical order
chapter 2 basic operations 2.5 manipulating registers 38 2.5.5 jumping from the register window this function enables a jump to the source line, disassembly start address, or memory address corresponding to a register value in the register window. a jump destination can be specified by selecting a desired register. the value of a selected register acts as a jump pointer. when a jump is made to the source window, a jump to that source line including the jump pointer is performed. jump destination procedure source window 1. select a register 2. select jump -> s ourcetext... from the menu bar. assemble window 1. select a register. 2. select jump -> a ssemble... from the menu bar. memory window 1. select a register. 2. select jump -> m emory... from the menu bar. a jump is made to the value of the selected register. in this case, address d0h, held in the bc register, is the jump pointrer. jump to the source window. a jump to that source line including address d0h in the source window is performed. jump to the assemble window
chapter 2 basic operations 2.6 creating events 39 2.6 creating events an event, set beforehand in a program, specifies that an operation is to be performed when a specified condition is satisfied. two types of conditions are used. one is an execution event, which is set for a program execution address. the other is an access event, which is set for memory data accessed by a programmed instruction. four types of events are used to perform operations. these include break events for terminating the program or analyzer, and qualified events, section events, and snapshot events which are used to control the tracer. the event-related windows are listed below. operation window event management event manager event condition event set dialog box event condition creation event link condition event link dialog box break condition break dialog box trace condition trace dialog box snapshot condition snap-shot dialog box event setting external sense clip condition external sense clip dialog box
chapter 2 basic operations 2.6 creating events 40 2.6.1 setting and referencing events in the source window and assemble window in the source window and assemble window, break events can be set, and events can be referenced. if a break event is set in the source window or assemble window, a parallel-linked event link condition, named break-l, is automatically created. all set break events become execution events (with the status set to run). function procedure break event setting use any of the five methods described below. 1. click the point mark area. 2. double-click a line number or address. 3. select a line number or address, then click the button. 4. select a line number or address, then select execute -> set b p from the menu bar. 5. select a line number or address, then press ctrl +b . event condition reference use either of the two methods described below. select an address or line number indicated by e in the point mark area, then perform either of the following operations: 1. click the button. 2. select view -> e vent? from the menu bar. event reference: when an event is referenced, the event manager is opened, and the event is marked. point mark area: a break event can be set simply by clicking this area. line number and address: an address displayed in reverse video becomes the pointer used for in p ut. break event setting
chapter 2 basic operations 2.6 creating events 41 2.6.2 creating event conditions event conditions are divided into two main types: execution events for detecting an execution address, and access events for detecting access data. when an execution event is used, it can be combined with an event condition. function procedure event condition creation the event set dialog box is used. select browse -> e vent -> e ventset... from the menu bar. event link condition creation 1. create an execution event in the event set dialog box. 2. open the event manager by selecting browse -> e vent -> eventmanager... from the menu bar. 3. open the event link dialog box by selecting browse -> e vent -> eventlinkset... from the menu bar. 4. create an event link condition by dragging & dropping the execution event created in 1., above. event condition creation: event set dialog box event condition link: event link dialog box an execution event is an event for which the status is run. event condition creation and registration use execution events. event link condition creation and registration event management: event manager
chapter 2 basic operations 2.6 creating events 42 examples of event condition setting are given below. when the event set dialog box is opened, the default screen, shown below, initially appears. modify the screen settings as required. <1> <3> <4> <2> <5> <6> <7> condition setting remarks when a program at address 0x100 is executed <1> 0x100 <2> 0 <3> run the defaults are used for <4> , <5> , <6> , and <7> . when memory access to address 0xfe00 is performed <1> 0xfe00 <4> 0x00 <2> 0 <5> ff <3> data r/w the defaults are used for <6> and <7> . when memory access is performed for addresses 0xfe00 to 0xfe7f <1> 0xfe00-0xfe7f <3> data r/w <5> ff <2> 0 <4> 0 the defaults are used for <6> and <7> . an event occurs when any address in the range is accessed. when memory is read (with no address condition set) <1> 0 <4> 0 <2> ffff <5> ff <3> data read the defaults are used for <6> and <7> . if bit 0 is 1 when writing to address 0xfb01 is performed <1> 0xfb01 <4> 1 <2> 0 <5> fe <3> data write the defaults are used for <6> and <7> . for mask specification, set those bits to be monitored to 0, and set the other bits to 1. when 0x10 is written to address 0xfb01 <1> 0xfb01 <4> 0x10 <2> 0 <5> 0 <3> data write the defaults are used for <6> and <7> . when an event is to be set at the start of function sub(), coded in c <1> _sub <2> 0 <3> run the defaults are used for <4> , <5> , <6> , and <7> . when the value of variable cnt, registered in c, becomes 0x46 <1> _cnt <4> 0x46 <2> 0 <5> 0 <3> data r/w the defaults are used for <6> and <7> . when an event is to be set with the start function of the assembler <1> start <2> 0 <3> run the defaults are used for <4> , <5> , <6> , and <7> . when the value of assembler variable data becomes 35h <1> data <4> 35h <2> 0 <5> 0 <3> data r/w the defaults are used for <6> and <7> .
chapter 2 basic operations 2.6 creating events 43 2.6.3 setting events event conditions registered in the event set dialog box or event link dialog box can be used as break conditions and trace conditions. condition procedure when used as a break condition select browse -> b reakset... from the menu bar. when used as a trace condition select browse -> trac e -> t raceset... from the menu bar. when used as a snapshot condition select browse -> trac e -> sn apshottraceset... from the menu bar. when used as an external sense clip condition select execute -> extsensecli p... from the menu bar. setting a break condition: break dialog box setting a snapshot condition: snap-shot dialog box setting a trace condition: trace dialog box setting a condition enabling the output of data to the external sense clip: external sense clip dialog box set an event in the desired dialog box by dragging and dropping from the event manager.
chapter 2 basic operations 2.6 creating events 44 2.6.4 saving and restoring event conditions event conditions can be saved to a file. saved event conditions can be referenced. event conditions are saved in text format, allowing an editor to be used to reference saved event conditions. to save an event condition to a file: 1. activate the event manager. 2. select file -> o pen/save condition -> sa ve file as... from the menu bar of the event manager. 3. save the event condition by using the view file save dialog box. to restore a saved event condition: 1. activate the event manager. 2. select file -> o pen/save condition -> o pen condition... from the menu bar of the event manager. 3. load the file containing the event condition to be restored with the view file load dialog box. saving an event condition to a file: view file save dialog box restoring an event condition saved to a file: view file load dialog box \ \
chapter 2 basic operations 2.6 creating events 45 2.6.5 functions available in the event manager the event manager allows the user to use a variety of functions such as enabling/disabling an event, deleting an event, and referencing an event. the available functions are listed below. function procedure enabling/disabling an event select an event to be enabled or disabled, then perform the following: to enable the event: click the button. to disable the event: click the button. deleting an event 1. select the event to be deleted. 2. click the button. detailed event condition display select view -> d etail from the menu bar of the event manager. changing the order of display the order of display can be changed using the menu bar of the event manager. to enable display in event name order: select view -> n ame. to enable display in type order: select view -> k ind. referencing/modifying an event condition 1. select the event to be referenced or modified. 2. select an option from operation in the menu bar of the event manager. event manager event manager (detailed display) referencing an event
chapter 2 basic operations 2.6 creating events 46 2.6.6 jumping to an event setting address this function enables a jump to the source line, disassembly start address, or memory address corresponding to the address of an event condition in the event manager. a jump destination can be specified by selecting an event condition. the start address of a selected event condition acts as a jump pointer. when a jump is made to the source window, a jump to that source line including the jump pointer is performed. jump destination procedure source window 1. select an event condition. 2. select jump -> s ourcetext... from the menu bar. assemble window 1. select an event condition. 2. select jump -> a ssemble... from the menu bar. memory window 1. select an event condition. 2. select jump -> m emory... from the menu bar. a jump is made to the address of the selected event, event02. in this case, the start address (d0h) of function main is the jump pointer. jump to the source window. a jump to that source line including address d0h in the source window is performed. jump to the assemble window
chapter 2 basic operations 2.7 manipulating symbols (variables) 47 2.7 manipulating symbols (variables) the user can display and modify the values of variables. before an operation such as symbol debugging can be performed, a load module file including debug information must be loaded. the user can enter symbols in the address and data input fields of each window. to enter symbols, observe the input formats indicated below. type of symbol input format variable defined in c _ fnc file #_ fnc variable defined in assembler language fnc file#fnc source line number file : no sfr sfrneme fnc: function name or variable name sfrname: sfr name file: file name no: line number 1. when specifying a variable defined in c, prefix the variable with an underbar (_). 2. use a sharp (#) as the separator between a file name and variable name. 3. use a colon (:) as the separator between a file name and line number. the windows related to symbol operations are listed below. operation window display of variables variable window registration of displayed variables add variable dialog box temporary display of variables variable view dialog box display of local variables local variable window
chapter 2 basic operations 2.7 manipulating symbols (variables) 48 2.7.1 displaying and modifying variables the user can display and modify the values of variables in the variable window, variable view dialog box, and local variable window. variable procedure display at all times display the variables in the variable window. select v iew -> w atch variable... from the menu bar. temporary display 1. select a source variable displayed in the source window. 2. select v iew -> v iew variable... from the menu bar, or click the button in the source window. display display of local variables select b rowse -> l ocal variable... from the menu bar. variable modification modifi- cation local variable modification use the variable window to modify a variable. use the local variable window to modify a local variable. both windows are modified as follows: 1. open the desired window. 2. switch to modify mode by clicking the button. 3. position the cursor to the variable to be modified, then modify the data. 4. after entering the new data, execute the modification by clicking the button. switch to view mode by clicking the button. registration the variable window allows the user to register a displayed variable. to register a variable in the source window: 1. select a source variable displayed in the source window. 2. select v iew -> w atch variable... from the menu bar, or click the button in the source window. to register a variable in the add variable dialog box for variable registration: 1. select v iew -> add var i able... from the menu bar. 2. register the variable in the add variable dialog box. deletion the user can delete any variable displayed and registered in the variable window. 1. select the variable to be deleted. 2. select o peration -> d elete from the menu bar.
chapter 2 basic operations 2.7 manipulating symbols (variables) 49 after a variable has been selected in the source window, that variable can be displayed or modified by clicking the watch button, or can be temporarily displayed by clicking the view button. display and modification of local variables: local variable window display and modification of variables: variable window temporary display of variables: variable view dialog box to register a variable by keyboard input, or to display a variable registered by the assembler in the variable window: add variable dialog box
chapter 2 basic operations 2.7 manipulating symbols (variables) 50 2.7.2 saving and referencing symbol data displayed symbol data can be saved to a file. a file containing saved symbol data can be referenced. symbol data is saved in text format, allowing an editor to be used to reference saved symbol data. to save displayed symbol data to a file: 1. activate the desired window. 2. when the variable window has been selected, select file -> o pen/save condition -> sa ve file as... from the menu bar. when the local variable window has been selected, select file -> save a s... from the menu bar. 3. save displayed symbol data by using the view file save dialog box. to open and reference a file containing saved symbol data: 1. activate the desired window. 2. when the variable window has been selected, select file -> o pen/save condition -> o pen condition... from the menu bar. when the local variable window has been selected, select file -> o pen... from the menu bar. 3. load the file to be referenced by using the view file load dialog box. saving displayed register data to a file: view file save dialog box reference window. load and open the file to be displayed. the window is opened for reference. all operations related to modification are disabled. displaying symbol data that has been saved to a file: view file load dialog box \ \
chapter 2 basic operations 2.7 manipulating symbols (variables) 51 2.7.3 functions available in the variable window and local variable window the variable window and local variable window give the user access to a variety of functions, such as the ability to modify the data number system. the available functions are listed below. function procedure display of variables of pointer type a variable of pointer type is prefixed by + or -. variable prefixed by +: the value of the variable indicated by the pointer is displayed by double-clicking. at this time, the prefix of the displayed variable changes to -. variable prefixed by -: the display of the value of the variable indicated by the pointer is stopped by double-clicking. at this time, the prefix of the displayed variable changes to +. number system display selection select view -> b in, o ct, d ec, h ex, or p roper from the menu bar. a variable prefixed by + or - is a variable of pointer type. double-clicking a variable of pointer type prefixed by + displays the value of the variable indicated by the pointer. at this time, the prefix of the displayed variable changes from + to -. variable window data display. tomodify button: used to modify data. the user can choose binary, octal, decimal, hexadecimal, or automatic for display.
chapter 2 basic operations 2.8 using the tracer effectively 52 2.8 using the tracer effectively the tracer records device operations in trace memory. the ie-78000-r-a has 32k frames of trace memory. trace memory has a ring buffer structure. for combined events, four trace methods are supported: trace cycle trace mode remarks machine cycle trace total trace port trace operation is possible. total trace trace operation is performed only when the device performs a read, write, or fetch operation. sectional trace the start and end of trace operation can be specified using an event condition. event cycle trace conditio- nal trace qualified trace trace operation is performed only when an event condition match is detected. the trace-related windows are listed below. operation window trace result display trace view window trace display show trace dialog box display item selection snapshot display snap trace dialog box trace condition setting trace dialog box snapshot condition setting snap-shot dialog box trace result search trace pick-up dialog box
chapter 2 basic operations 2.8 using the tracer effectively 53 2.8.1 displaying trace results trace results can be displayed in the trace view window. to display trace results: select browse -> trac e -> tracev iew... from the menu bar, or click the button. display of fetch-type access results. the results of program execution are displayed. trace status. statuses such as the ie status at trace stop are displayed. display of data access results. the results of r/w accesses to memory are displayed. the execution time between frames is counted. frame number external sense clip input/output results are displayed. port trace results. in machine cycle trace, port trace operation is possible. disassembly display. this display is provided when fetch-type access is performed and the status is m1. item description frame displays trace frame numbers. valid range: 0 < trace frame number < 32,767 time displays the number of clock pulses taken by the target chip between the start of execution of the immediately preceding trace address and the start of execution of the current trace address. for the clock signal, the cpu clock is not used. instead, the 10-mhz clock signal of the in-circuit emulator is used. measurement range: 1 < time tag < 0xffffff address data statu displays program fetch results. this field displays the following information depending on the fetch status displayed in the status field: m1 : fetch of the first byte of an instruction op : operation code fetch if : invalid fetch address data statu displays data access results. this field displays the following information depending on the access status display in the status field: vect : vector read r : data read w : data write extp displays the input level of the external sense clips when trace has been performed. disasm displays the results of disassembly. this information is displayed only when the fetch status is m1 .
chapter 2 basic operations 2.8 using the tracer effectively 54 2.8.2 saving and referencing trace results trace results can be saved to a file. a file containing saved trace results can be referenced. trace results are saved in text format, allowing an editor to be used to reference saved trace results. to save trace results to a file: 1. activate the trace view window. 2. select file -> save a s... from the menu bar. 3. save trace results with the view file save dialog box. to open and reference a file containing saved trace results: 1. activate the trace view window. 2. select file -> o pen... from the menu bar. 3. load the file to be referenced by using the view file load dialog box. saving displayed data to a file: view file save dialog box displaying data saved to a file: view file load dialog box reference window. load and open the file to be displayed. the window is opened for reference. if the range to be saved consists of about 100 frames or more, a dialog box for reporting the save status is opened. to stop the save operation, click the stop button. \ \
chapter 2 basic operations 2.8 using the tracer effectively 55 2.8.3 effective trace memory usage 1 (trace mode setting) trace memory can be used effectively by setting a trace condition and trace mode. three major trace modes are supported: trace mode description total trace all accesses are traced. the user can choose between machine cycle trace and event cycle trace. sectional trace a section from one event to another is traced. this mode is useful, for example, for tracing one particular function. qualified trace only an event condition match point is traced. this mode is useful, for example, for tracing particular memory accesses. each trace mode is described below. 1. the data for each of the following modes indicates the results of executing test program 1 from address 80h to address 8eh. 2. test program 1 initializes, to zero, the four bytes of memory from address 0fe00h to address 0fe03h. test program 1: clearing ram addr data mnemonic 0080 61d0 sel rb0 0082 16fffc movw hl,#0fcffh 0085 a100 mov a,#0h 0087 a304 mov b,#4h 0089 bb mov [hl+b],a 008a 8bfd dbnz b,$89h 008c 00 nop 008d 00 nop 008e fafe br $8eh selects register bank 0. sets the initialization start address, minus 1. sets initialization data. sets the number of bytes to be initialized. initializes memory. determines termination.
chapter 2 basic operations 2.8 using the tracer effectively 56 1. results of total trace (event cycle trace) the results of total trace are indicated below. all accesses are traced, so that all program operations can be identified. program fetch operations, and data read and write operations are traced. frame faddr fdat fstat maddr mdat mstat disasm 32738 0080 61 m1 sel rb0 32739 0081 d0 op 32740 0082 16 m1 movw hl,#0fcffh 32741 0083 ff op 32742 0084 fc op 32743 0085 a1 m1 mov a,#0h 32744 0086 00 op 32745 0087 a3 m1 mov b,#4h 32746 0088 04 op 32747 0089 bb m1 mov [hl+b],a 32748 008a 8b m1 dbnz b,$89h 32749 fd03 00 w 32750 008b fd op 32751 0089 bb m1 mov [hl+b],a 32752 008a 8b m1 dbnz b,$89h 32753 fd02 00 w 32754 008b fd op 32755 0089 bb m1 mov [hl+b],a 32756 008a 8b m1 dbnz b,$89h 32757 fd01 00 w 32758 008b fd op 32759 0089 bb m1 mov [hl+b],a 32760 008a 8b m1 dbnz b,$89h 32761 fd00 00 w 32762 008b fd op 32763 008c 00 m1 nop 32764 008d 00 m1 nop 32765 008e fa m1 br $8eh 32766 008f fe op total trace mode is set as follows: 1. disable all trace event conditions. 2. select a trace cycle. select execute -> trac e -> m achine all. trace or e vent all. trace from the menu bar.
chapter 2 basic operations 2.8 using the tracer effectively 57 2. results of sectional trace the results of sectional trace from address 89h to address 8ch are shown below. the range to be traced can be specified, such that trace memory is used effectively. frame faddr fdat fstat maddr mdat mstat disasm 32750 0089 bb m1 mov [hl+b],a 32751 008a 8b m1 dbnz b,$89h 32752 fd03 00 w 32753 008b fd op 32754 0089 bb m1 mov [hl+b],a 32755 008a 8b m1 dbnz b,$89h 32756 fd02 00 w 32757 008b fd op 32758 0089 bb m1 mov [hl+b],a 32759 008a 8b m1 dbnz b,$89h 32760 fd01 00 w 32761 008b fd op 32762 0089 bb m1 mov [hl+b],a 32763 008a 8b m1 dbnz b,$89h 32764 fd00 00 w 32765 008b fd op 32766 008c 00 m1 nop sectional trace mode and the event conditions can be set as shown below. by enabling trace event conditions, a conditional trace operation can be performed. set sectional trace conditions as follows: start: event01 end: event02 event occurrence conditions event01: execution of address 89h event02: execution of 8ch
chapter 2 basic operations 2.8 using the tracer effectively 58 3. results of qualified trace the results of qualified trace, for data read and write operations only, are indicated below. only those points that are to be traced are traced, allowing large amounts of data to be traced. note, however, that since trace is performed only when an event condition match is detected, the context is difficult to grasp. frame faddr fdat fstat maddr mdat mstat disasm 32763 fd03 00 w 32764 fd02 00 w 32765 fd01 00 w 32766 fd00 00 w qualified trace mode and an event condition can be set as shown below. by enabling a trace event condition, a conditional trace operation can be performed. set a qualified trace condition as follows: event03 event condition event03: when data read or write is performed at any address
chapter 2 basic operations 2.8 using the tracer effectively 59 2.8.4 effective trace memory usage 2 (trace full break, snapshot trace) trace full break 1. trace memory has a ring buffer structure. this means that, once the trace memory is filled with trace data, the existing trace data is overwritten by the new data, starting from the oldest data. 2. to preserve the trace results, trace operation can be stopped once the trace memory is full. trace full break setting: select execute -> trace f ull break from the menu bar. snapshot trace 1. trace memory is used to store the execution history. in addition to the execution history, other data can be stored by specifying a snapshot event. 2. the snapshot trace function writes specified data into trace memory when a condition is satisfied. the following data can be written: data description register all registers of the current bank (pc, sp, psw, ax, bc, de, hl) sfr data memory up to five points in sfrs or memory can be traced. 3. before data is written into trace memory, the execution of the user program is stopped. 4. for the program below, the method of writing the register and sfrs (p0, p1) when address 0fd02h is accessed is shown. test program 1: clearing ram addr data mnemonic 0080 61d0 sel rb0 0082 16fffc movw hl,#0fcffh 0085 a100 mov a,#0h 0087 a304 mov b,#4h 0089 bb mov [hl+b],a 008a 8bfd dbnz b,$89h 008c 00 nop 008d 00 nop 008e fafe br $8eh selects register bank 0. sets an initialization start address, minus 1. sets initialization data. sets the number of bytes to be initialized. initializes memory. determines termination.
chapter 2 basic operations 2.8 using the tracer effectively 60 example of snapshot event setting event condition: address: 0fd02h status : data r/w data : all data snapshot condition: event: event 01 snapshot data: registers, sfrs (p0, p1) trace data pc sp psw x:r0 a:r1 c:r2 b:r3 de:rp2 hl:rp3 mem1(dat) mem2(dat) frame faddr fdat fstat maddr mdat mstat disasm 32742 0089 bb m1 mov [hl+b],a 32743 008a 8b m1 dbnz b,$89h 32744 fd03 00 w 32745 008b fd op 32746 0089 bb m1 mov [hl+b],a 32747 008a 8b m1 dbnz b,$89h 32748 fd02 00 w 32749 008b fd op 0089 fee0 02 00 00 00 02 0000 fcff p0(00) p1(00) 32755 0089 bb m1 mov [hl+b],a 32756 008a 8b m1 dbnz b,$89h 32757 fd01 00 w 32758 008b fd op 32759 0089 bb m1 mov [hl+b],a 32760 008a 8b m1 dbnz b,$89h 32761 fd00 00 w 32762 008b fd op in frame 32748, a match with event condition event01 was detected, causing snapshot event snap to occur. between frame 32749 and frame 32755, the debugger stopped once to write snapshot data into the tracer.
chapter 2 basic operations 2.8 using the tracer effectively 61 2.8.5 inter-window connection functions (window connection function, jump function) window connection function: this function displays trace results in each window. when the user positions the cursor to the trace view window, each of the windows (source window, assemble window, and memory window) can be manipulated interactively, thus allowing trace operation in each window. jump function: a jump can be made to a position in the source window, assemble window, and memory window corresponding to the address value of a frame line specified in the trace view window. when the window connection function is used, the trace view window remains active. when the jump function is used, however, the jump destination window becomes the active window. function operation connection to the source window activate the trace view window. select window connect -> s ourcetext from the menu bar. connection to the assemble window activate the trace view window. select window connect -> a ssemble from the menu bar. window connection function connection to the memory window activate the trace view window. select window connect -> m emory from the menu bar. jump to the source window select a frame in the trace view window. select jump -> s ourcetext... from the menu bar, or press ctrl +u . jump to the assemble window select a frame in the trace view window. select jump -> a ssemble... from the menu bar, or press ctrl +a . jump function jump to the memory window select a frame in the trace view window. select jump -> m emory... from the menu bar, or press ctrl +m .
chapter 2 basic operations 2.8 using the tracer effectively 62 with the window connection function and jump function, connection is made to the data in each window as follows: function window connection jump function source window assemble window fetch address fetch address memory window data read address and data write address fetch address, data read address, and data write address for window connection and jump for window connection and jump for jump for window connection and jump
chapter 2 basic operations 2.9 measuring the execution time 63 2.9 measuring the execution time the ie-78000-r-a has two timers. one timer measures the time from the start of execution to the end of trace operation. the other timer measures the time from the start of the previous trace operation to the start of the current trace operation. the specifications of the two timers are as follows: timer maximum measurement time minimum measurement time for execution time measurement approx. 14 minutes and 18 seconds approx. 500 nanoseconds for trace interval measurement (time tag) approx. 1.677 seconds approx. 100 nanoseconds 2.9.1 measuring program execution time the time from the start of program execution to the end of program execution is displayed in the timer window. the measurement time depends on the execution mode, as indicated below. execution mode measurement section step execution last instruction real-time execution from the start of execution to a break non-break real-time execution from the start of execution to termination of the tracer the timer window can be opened as follows: execution time display: select browse -> t imer... from the menu bar, or press the button. file o peration
chapter 2 basic operations 2.9 measuring the execution time 64 2.9.2 time measurement using the tracer for measurement of a short section, regularly executed processing, and so forth, the time tag is useful. when compared with the execution times displayed in the timer window, shorter times are obtained with the time tag. however, the time tag stores multiple data items in trace memory, so that information such as time distribution data can be checked using a separate tool. with the time tag, the time from the start of the previous trace operation to the start of the current trace operation is measured. this measurement is conducted not only while the program is being executed but also while the program is stopped. this means that the time tag data for the first program execution frame is meaningless. time tag. the interval from the previous frame to the current frame is displayed. an actual time, counted in 100 ns steps, is converted to a hexadecimal number for display. to convert a displayed value to an actual time, convert the displayed value to a decimal number, then multiply that number by 100 ns.
chapter 3 advanced use of ID78K0 65 chapter 3 advanced use of ID78K0 this chapter describes several advanced uses of the ID78K0. note that these uses are usually not essential to normal operation. 3.1 verifying the validity of evaluation evaluation is essential to the development of a program. if the evaluation of a particularly important item is omitted for some reason, bugs may remain in a program that is offered for retail sale. this section describes the use of the coverage functions to verify the validity of evaluation. 3.2 using external sense clips the in-circuit emulator status or the contents of memory can be output in real time, by using external sense clips together with event conditions. this section describes the use of the external sense clips. 3.3 measuring time by setting conditions basically, the timer window of the ID78K0 supports only the measurement of the time that elapses between the start and end of program execution. shorter periods can, however, be measured by using the tracer in combination with events.
chapter 3 advanced use of ID78K0 3.1 verifying the validity of evaluation 66 3.1 verifying the validity of evaluation evaluation is essential to the development of a program. if the evaluation of a particularly important item is omitted for some reason, bugs may remain in a program that is offered for retail sale. this section describes the use of the coverage functions to verify the validity of evaluation. note, however, that the validity of evaluation cannot be completely verified based on only the results of coverage. 3.1.1 coverage coverage is a record of the flow of the execution of a program. while the tracer can trace program execution backwards, coverage merely indicates whether specified instructions within a program have actually been executed. the debugger supports coverage for the read, write, and fetch operations. the results of coverage can be displayed in the coverage window. the following window and dialog boxes are used for coverage: window description coverage window displays the results of coverage. coverage efficiency view dialog box displays the coverage results, as a percentage, for each function or specified address range. coverage condition setting dialog box used to add items to be displayed in the coverage efficiency view dialog box. coverage memory clear dialog box initializes the coverage memory. coverage window coverage efficiency view dialog box coverage memory clear dialog box coverage condition setting dialog box
chapter 3 advanced use of ID78K0 3.1 verifying the validity of evaluation 67 3.1.2 verifying the validity of evaluation based on coverage ideally, all possible patterns of program execution should be evaluated. due to time or other restrictions, however, evaluation may have to be restricted by, for example, sampling and combining several patterns. evaluation based on sampled patterns must, however, be checked for validity. one method of verifying the validity of evaluation is the use of the coverage results to check whether all instructions have been executed. the above check can easily be performed by using the coverage window and the memory map in the link list file (.map), output upon linkage of the program. verification based on coverage 1. refer to the memory map in the link list file to identify any free spaces (* gap *) in the program. 2. refer to the contents of the coverage window to check whether all memory spaces other than the free spaces, identified in step 1, have been accessed (read, written, or fetched). 3. if any unaccessed space is revealed by step 2, check the program and review the evaluation items. if any free space in the program has been accessed, check that space by, for example, setting event conditions. example link list file *** memory map *** space=regular memory=rom base address=0000h size=8000h output input input base size segment segment module address @@vect00 0000h 0002h cseg at @@vect00 @cstart 0000h 0002h * gap * 0002h 0012h @@vect14 0014h 0002h cseg at @@vect14 sample 0014h 0002h * gap * 0016h 002ah @@calt 0040h 0000h cseg callt0 @@calt @cstart 0040h 0000h @@calt sample 0040h 0000h @@calt c_sub 0040h 0000h * gap * 0040h 0040h intermediate lines omitted @@cnst 0080h 0000h cseg unitp @@cnst @cstart 0080h 0000h @@cnst sample 0080h 0000h @@cnst c_sub 0080h 0000h @@code 0080h 02d1h cseg @@code @cstart 0080h 0050h @@code sample 00d0h 0130h in this example, 0002h to 0013h, 0016h to 003fh, and 0040h to 007fh are free spaces.
chapter 3 advanced use of ID78K0 3.1 verifying the validity of evaluation 68 example coverage results (results of executing the example link list file) unaccessed spaces in this example, the reset vector at addresses 0 and 1 has not been accessed. the operation performed upon a reset must, therefore, be evaluated.
chapter 3 advanced use of ID78K0 3.1 verifying the validity of evaluation 69 3.1.3 notes on coverage results when checking the coverage results, note the results of conditional branches. the ie-78000-r-a supports c0 coverage, which cannot be used to check how processing has branched at a conditional branch instruction. example of execution of a conditional branch instruction 1. when the following program is executed from address 80h to 8ch, a conditional branch instruction is executed at address 86h. execution jumps to address 88h because the condition is false. addr data mnemonic 0080 a101 mov a,h ; assume that the h register contains 1. 0082 a302 mov b,#2h 0084 4d01 cmp a,#1h 0086 bd02 bnz $8ah 0088 610b add a,b 008a a200 mov c,#0h 008c 00 nop 2. the coverage results are as follows, indicating that all instructions have been executed. all instructions at addresses 80h to 8ch have been executed. 3. actually, however, the condition may be true, depending on the stored data, thus causing address 88h to be skipped. in such a case, the coverage results do not cover all evaluation items.
chapter 3 advanced use of ID78K0 3.2 using external sense clips 70 3.2 using external sense clips external sense clips have various functions. they can be used to post notification of the in- circuit emulator status or output 1-byte ram data in real-time. the use of external sense clips may enable essential processing which has not been possible conventionally. external sense clips no. 01 to 08 are provided. the debugger handles them as bits 0 to 7, respectively. external sense clip number debugger handles as: no.08 bit 7 no.07 bit 6 no.06 bit 5 no.05 bit 4 no.04 bit 3 no.03 bit 2 no.02 bit 1 no.01 bit 0 when external sense clips are set to output mode, they must be pulled up using resistors. in such a case, a voltage exceeding +15 v cannot be applied to the sense clips. the tracer traces the potential difference between each external sense clip and gnd, regardless of whether the sense clips are set to input or output mode. the hc4050b (used as an input buffer) determines whether the trace data for each external sense clip is 1 or 0. the trace data for external sense clips can be used for event conditions, thus enabling the setting of a wide range of event conditions.
chapter 3 advanced use of ID78K0 3.2 using external sense clips 71 3.2.1 tracing external data to trace the state of each pin of the target device, set the external sense clips to input mode (default). input data can be incorporated into event conditions, such that an event can be triggered by an external source. setting procedure 1. set the external sense clips to input mode. set to input mode. 2. connect external sense clips to the pins to be traced. 3. to set an event, set event conditions using the event set dialog box. the results of trace can be checked using the trace view window. trace data for external sense clips set this area to incorporate external sense clip data into the event conditions.
chapter 3 advanced use of ID78K0 3.2 using external sense clips 72 3.2.2 trigger output to output the in-circuit emulator status or other data, set the external sense clips to trigger output mode. set to trigger output mode trigger output data is output under the following condition: trigger output condition when the pass count becomes 0 upon the occurrence of a break event trigger data is not output upon the occurrence of a fail-safe or manual break. trigger output data is output from external sense clip no. 01. when external sense clips are set to output mode, they must be pulled up using resistors. vdd(max:15v) r connect external sense clip no. 01. trg out trigger condition satisfied vdd gnd connection diagram trigger output waveform trg out time t
chapter 3 advanced use of ID78K0 3.2 using external sense clips 73 3.2.3 real-time ram output the ie-78000-r-a does not support real-time ram sampling. only 1-byte data in memory can be output in real-time, by using event conditions in combination with external sense clips and simple external jigs. create an access event. in this example, the contents of address 0xfe00 are output. drag & drop the event into the event setting area, then select output. because data is being output in real time, it can also be used as a trigger source for other targets. when external sense clips are set to output mode, they must be pulled up using resistors. vdd(max:15v) r connect each external sense clip. example connection gnd no.01 - no.08 led transition of data output from external sense clip data the set event occurs. latch the contents of the data bus upon the occurrence of the set event. the latched data is held until the next occurrence of the event.
chapter 3 advanced use of ID78K0 3.2 using external sense clips 74 3.2.4 creating an event by anding a data condition advanced events can be created by using external sense clips. an event condition can be created by anding a data condition, as follows: procedure for creating an event condition by anding a data condition 1. create an event having a data condition. 2. set the event created in step 1 as an output condition for the external sense clips. 3. pull up the eight external sense clips using resistors. 4. create an event having an address condition or execution condition. 5. specify an external sense data condition for the event created in step 4, thus creating an event having a condition anding those specified in steps 1 and 4. example causing an event to occur when 15h is written into address 0fe12h, provided address 0fe00h contains 20h set address, status, and data. set external as the default or mask in ff. set an event condition, and set the external sense clips to output mode. finally, set address, status, and data for another event. specify the value at address 0fe00h for external. in this example, one data condition is anded with another data condition. a data condition can also be anded with an execution condition. an event condition like that shown above can be set for various events, thus enabling the creation of advanced events. first try specifying "on."
chapter 3 advanced use of ID78K0 3.3 measuring time by setting conditions 75 3.3 measuring time by setting conditions the timer measurement function of the ie-78000-r-a does not support the setting of event conditions. the user may, however, require information such as the intervals that elapse between a function being called, or whether timer interrupts are generated correctly and on time. time measurement using event conditions in combination with the tracer is described below. setting procedure 1. set an event at the beginning of the function for which time will be measured. the following program is used as an example: example program to be subject to time measurement addr data mnemonic > 0080 a300 mov b,#0h 0082 43 inc b t 0083 63 mov a,b ; set an event. 0084 8bfe dbnz b,$84h 0086 73 mov b,a 0087 faf9 br $82h this program executes an infinite loop between addresses 82h and 87h. the intervals (s) between the executions of the instruction at address 83h are measured. 2. set event and trace conditions as follows: set an event at the beginning of the processing to be subject to time measurement. set a qualified event.
chapter 3 advanced use of ID78K0 3.3 measuring time by setting conditions 76 3. after the event and trace conditions have been set, the execution of the program is traced as follows: check that the execution times are satisfactory by converting the time tag data to an actual time by using, for example, spreadsheet software. 4. save the trace results to a file. the execution times can be obtained by converting the time tag data to actual times by using, for example, spreadsheet software. conversion results frame number time tag data [hex] actual time [ m m s] 32666 0x2671 984.1 32667 0x2756 1007.0 32668 0x283b 1029.9 32669 0x291f 1052.7 32670 0x2a14 1077.2 32671 0x2aea 1098.6 32672 0x2bce 1121.4 32673 0x2cb3 1144.3 32674 0x2d98 1167.2 time tag data is counted every 100 ns. to obtain an actual time, convert hexadecimal to decimal, then convert the radix.
appendix a error messages 77 appendix a error messages this appendix lists the error and warning messages output by ID78K0. an error message consists of error number + type + message . error number type message a type is represented by an alphabetic character. there are three types: type explanation a abort error. processing is interrupted and the debugger ends. if this error occurs, debugging cannot be continued. f format (syntax) error. processing is interrupted. the currently open windows and dialog boxes are closed. w warning. processing is interrupted. the currently open windows and dialog boxes remain as is. a message contains the names of the file, variable, and device related to the error, as follows: representation in message explanation xxx low-order three digits of device name yyy file name zzz function name
appendix a error messages 78 error messages (1/9) error no. type message explanation --- -- cant open this file. please make sure, now active window. the project file format is incorrect, or the file content has collapsed. loading the project file was discontinued. --- -- cannot find character string. the search character was not found. the search was discontinued. alternatively, opening the specified file was discontinued because no data was in the file. --- -- event name is not set. there is no event name. specify the name of the event when adding it. --- -- event number already exist. it is impossible to add an event having the same number as an existing event. change the number of the event to be added or of the existing event. --- -- not enough memory. because of insufficient memory, a window cannot be displayed, its content cannot be changed, or changes to it cannot be retained. assign sufficient memory, and retry. --- -- other view mode window exist. two or more active windows of the same type cannot be opened simultaneously. an active window that was already open was closed. --- -- sorry, too large view file. the specified view file (.mem, .tvw, or .dis) contains more than 1000 lines. its display was discontinued. --- -- event name is already exist. it is impossible to add an event having the same name as an existing event. change the name of the event to be added or of the existing event. 0001 a communication open error communication with the in-circuit emulator (ie) is not possible. 0003 a hardware error a hardware error is detected. 0004 a monitor time out data was not transferred to and from the monitor program. clock pulses may not be being supplied to the target cpu or power may not be supplied. check the above and restart the debugger. 0005 a not found monitor file the monitor file is not found. 0006 a monitor file error a monitor file error is detected. 0009 a communication failed communication with the ie failed. 000a a verify error a verify error is detected. 000e a user program cannot run the user program cannot be executed. 000f a illegal receive data an illegal response is received. 0012 a emulation-board conflicts with device-file the em board id does not match the value in the device file. 0014 w target power off the power of the target device is off. 0015 w program is running the user program is running. 0016 w already break the user program is already in the break status. 0017 w tracer is running the tracer is running.
appendix a error messages 79 error messages (2/9) error no. type message explanation 0018 w timer is running timer measurement is in progress. 001d w measure is off timer measurement is not performed. 0020 w execution mode error an execution mode error is detected. 0021 w mapping error a mapping error is detected. 0022 w trace block not found the specified trace block does not exist. 0023 w there is no trace data there is no trace data. 0024 w trace range over the trace range has been exceeded. 0026 w bus hold mode the bus hold mode is active. 0077 f search data not found the search data does not exist. 0078 f measure overflow the timer measurement result overflowed. 007a f not specified coverage range the coverage range has not been specified. 007e w event no.3 is using event condition no. 3 is in use. 00c8 w user program is stepping the user program step is being executed. 01a1 a invalid ex78kx.om0 the executor file (ex78k0.om0) was not read correctly. the executor file may not exist or may have been destroyed. install the executor file again and restart the debugger. 01a3 a unconnected emulation-board the emulation board (ie-780xx-r-em) is not correctly connected. connect the ie-780xx-r-em to the ie-78000-r-a correctly. 01a5 a unconnected i/o emulation-board emulation board 1 (ie-78xxx-r-em1) is not correctly connected. connect the ie-78xxx-r-em1 to the ie-78000-r-a correctly. 01a6 a executor is running the executor is running. 01a8 a invalid expc.ini the initialize file (expc.ini) was not read correctly. the initialize file may not exist or may have been destroyed. install the initialize file again and restart the debugger. 0600 a communication buffer error the area for the buffer used for exchanging data with the ie was not reserved. end other ms- windows applications, change the setting of the ms- windows swap file, or install additional main memory in the host machine. 0f13 a send timed out data transmission to the ie failed. possible causes include an invalid interface board setting and ie power off condition. install the initialize file again, then restart the debugger. 0f14 a receive timed out no response was received from the ie. the ie may be abnormal. check the ie and restart the debugger. 0f15 a invalid d0xxx.78k the device file (d0xxx.78k) cannot be read correctly. the device file may not be located in the specified directory or it may have been destroyed. install the device file again, then restart the debugger.
appendix a error messages 80 error messages (3/9) error no. type message explanation 1000 a failure in initialization an attempt to initialize the ie failed. check whether the ie is abnormal. 1003 f illegal relocation address it is impossible to relocate to a specified address. 1004 f illegal parameter the parameter is illegal. 1006 f illegal address the address is illegal. 1007 a not enough substitute memory an attempt was made to map ie alternate memory in an area of 64k bytes or more. 100b f program is running a user program is running. this command cannot be executed. 100c f different bussize an attempt was made to make duplicate specification in areas having different bus sizes. 100d f total maximum over an attempt was made to specify a bus larger than the maximum size (8). 100e f enable maximum over the bus size is larger than 8. 100f w wrong target status(power off) the target state is unstable. 10ff a communication error it is impossible to communicate with the ie. check whether the ie is abnormal. 2000 f illegal sfr name the sfr name is illegal. 2002 f user program is running a user program is running. this command cannot be executed. 2003 f illegal sfr number an attempt was made to access a nonexistent sfr. 2004 f illegal bit number there is no bit sfr at the specified bit position. 2005 w redraw sfr name the sfr has been disabled from redrawing. 2006 f this sfr is hidden sfr this sfr is not open to general use. it is impossible to display or change data for the sfr. 2007 f cant read/write an attempt was made to write to a write-protected sfr or read from a read-protected sfr. 2008 f too big number the specified sfr was not found. 200a f illegal bit pattern an attempt was made to specify an illegal value for an sfr. 20ff a communication error communication with the ie is impossible. check whether the ie is abnormal. 3000 f illegal address the address is illegal. 3001 f different data there is a memory content mismatch. 3002 f illegal source address the specified source address range does not fall within the mapping range (during a memory search, comparison, or copy). 3003 f illegal destination address the specified destination address range does not fall within the mapping range (during a memory search, comparison, or copy). 3004 f illegal address (source & destination) the specified address range does not fall within the mapping range (during a memory search, comparison, or copy). 3005 f illegal parameter the parameter is illegal. 3006 f user program is running a user program is running. this command cannot be executed. 3008 f no parameter there is no parameter.
appendix a error messages 81 error messages (4/9) error no. type message explanation 3009 f parameter size alignment error the parameter size is illegal. change the parameter according to the memory access size. 300a f memory alignment error the address value is illegal. change the address value according to the memory access size. 300b f source start address alignment error the source address is illegal. change the source address according to the memory access size. 300c f error, destination start address alignment error in the destination address range, a memory range with a conflicting access memory size was specified. 300d f end address alignment error the end address is illegal. change the end address according to the memory access size. 300e f different access size in this area in the address range, a memory range with a conflicting access memory size was specified. 300f f different access size in source area in the source address range, a memory range with a conflicting access memory size was specified. 3010 f different access size in destination area in the destination address range, a memory range with a conflicting access memory size was specified. 3011 f different access size, source & destination the access size conflicts between the source and destination address ranges. 30ff a communication error communication with the ie is impossible. check whether the ie is abnormal. 4000 f number is referenced now the specified event condition cannot be deleted. 4001 f illegal table number the specified table number is illegal. 4002 f illegal start address the start address is illegal. 4003 f illegal end address the end address is illegal. 4004 f illegal status the status is illegal. 4005 f illegal data the data is illegal. 4006 f cant action number an attempt was made to use an event number that was already in use. 4007 f cant empty number an attempt was made to register more than 32,767 events of the same type. 4008 f table not found the specified event has not been registered. 4009 f illegal data size the data size is illegal. 400a f illegal type mode the mode is illegal. 400b f illegal parameter the parameter is illegal. 400c f illegal type number the type is illegal. 400d f table overflow an attempt was made to register more than 32,767 events of the same type. 400e f no entry event number the specified event does not exist. 400f f illegal elink data an event condition specified with a range condition or pass condition was used as an event link condition. alternatively, only one event condition was specified. 4010 f function not found the specified function was not found. 4011 a no free memory there is no sufficient memory. end unnecessary applications, or close the debugger window. 4012 f timer not enabled the timer is disabled. enable it if timer measurement must be made.
appendix a error messages 82 error messages (5/9) error no. type message explanation 4013 w data access size mismatch at the bus size the access size in an event condition does not match the bus size for mapping. 4014 f cant use software break at present, no software break can be used. specify that a software break be usable, using the extended option dialog box. 4015 f not point-address it is impossible to use, as an address condition, an event condition specifying a range. 4016 f not renew event condition. this event condition is being used for another event. it is impossible to change the address range condition or pass count condition. 4017 f specified odd-address by word- access. the data value was not detected in word data beginning at an odd address. do not include that data value in the setting. 5000 a illegal type number the type is illegal. 5002 a illegal file name the device file cannot be opened. 5003 a cannot file seek an attempt to seek the file failed. 5004 a cannot file close an attempt to close the file failed. 5005 a illegal device format the format of the device file is illegal. 5006 a cannot device initialize an attempt to initialize the ie failed. 5007 a illegal device information there is no device information. 5008 f cannot open device file the specified device file cannot be opened. 5009 f cannot open ex78kx.om0 file the ex78k0.om0 cannot be opened. 500a f no match device file of version the version of the device file is illegal. 500b w device has no relocatable iram. the currently selected device does not support relocation in internal ram. 6001 f illegal entry symbol name the symbol name is illegal. 6002 f illegal parameter the parameter is illegal. 6003 f illegal entry function name the function name is illegal. 6004 f out of buffer flow function display in the stack window is incomplete. the maximum allowable line size is 512 characters. 6005 f illegal expression the expression is illegal. 7001 f user program is running a user program is running. this command cannot be executed. 7002 f user program is stopped a user program is at a break. this command cannot be executed. 7003 f trace function is active the tracer is running. this command cannot be executed. 7004 f trace memory is off the tracer is off. 7005 f no return address, cant execute the return address of the current function was not found. step execution based on the return command is not carried out. 7010 w warning, no source line information instruction-level step execution was carried out because there was no source information. 7012 a not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window.
appendix a error messages 83 error messages (6/9) error no. type message explanation 70fe a bus hold error the bus is on hold. the user program cannot be executed. 70ff a communication error communication with the ie is impossible. check whether the ie is abnormal. 7801 f step wait canceled step execution was discontinued. so, communication with the ie may become impossible. 7802 f step aborted an illegal access break occurred during step execution. check the user program. 7f00 f interrupted step step execution was forced to end. 7f02 f suspended step step execution was suspended. 7f03 a run/step cancel failed. cpu resetted an attempt to break the user program failed. the ie is unstable because the evaluation chip was reset. make sure that the ie is normal, then restart it. 7f04 f illegal address an attempt was made to execute in an non-mapped area. 8000 f file not found the file was not found. 8001 f illegal line number the line number is illegal. 8002 f current data is not set the current information has not been set. 8003 f ilegal address the address is illegal. 9002 f illegal set value the specified value cannot be set in a register. specify a value that can be set. a001 f illegal expression the expression is illegal. a002 f start address bigger than end address the start address is greater than the end address (start address > end address). check the addresses. a003 f source path not found the specified source path information is illegal. specify the correct source path information. a004 f expression is too big the size of the expression is greater than 127 characters. a005 a not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window. a006 f illegal argument the argument is illegal. a008 f source path not set the source path has not been specified. a009 f file not found the file was not found. a00a f file not open the file cannot be opened. a00b a file not close an attempt to close the file failed. a00c a file not read an attempt to read the file failed. it is likely that the file has collapsed. a00d f not source file of lm the specified source file has not been registered for the load module file. a file not registered for the load module file cannot be displayed in the source window. a00e f illegal line number the line number is illegal. a00f f illegal variable the variable does not exist. a010 a communication failed communication with the ie is impossible. check whether the ie is abnormal.
appendix a error messages 84 error messages (7/9) error no. type message explanation a011 f cant access register the register cannot be accessed. check the ie. a012 f cant access memory the specified memory (variable) cannot be accessed. check the ie or map setting. b000 f command line error the parameter is illegal. b001 f task type not found the load module file does not contain program information. b002 f file not found the file was not found. b003 f function not found the specified function was not found. b004 f illegal magic number the magic number for the load module file is illegal. b005 f symbol not found the symbol was not found. b008 f illegal value the expression is illegal. b009 a not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window. b00a f illegal symbol entry there is an illegal symbol in the load module file. it is likely that there is a bug related to the programming language. b00b f current type noting there is no debug information. load the load module file. b00c f current file noting there is no current source file. alternatively the source file cannot be opened because the load module file has not been loaded. b012 f line number too large the line number is illegal. b015 a read error an attempt to read the file failed. it is likely that the file has collapsed. b016 a open error the file cannot be opened. b017 a write error an attempt to write to the file failed. b019 a seek error an attempt to seek the file failed. b01a a close error an attempt to close the file failed. b01d f address not found there is no source line that corresponds to the current pc value. b01e f no line information(not compile with -g) there is no source line information in the load module file. attach the debug option, and carry out recompilation, assembly, and linkage. b01f f cannot find member no member was found in the specified structure. b020 f cannot find value the specified enumeration constant is illegal. b021 f striped lm there is no symbol information in the load module file. b022 f null statement line the line number is illegal. b026 f max dimension array over a four-dimensional or greater-scale array cannot be displayed. b027 f end of file the file is not complete. b029 f illegal address the address is illegal. b02a a communication failed communication with the ie is impossible. check whether the ie is abnormal. b02b f no stack frame point stack tracing is impossible with the current pc value.
appendix a error messages 85 error messages (8/9) error no. type message explanation b02c f max block overflow the maximum number of blocks in one function is exceeded. the function cannot be displayed. (the maximum number of blocks per function is 256.) b02d f illegal argument the argument is illegal. c001 f cannot open file the file cannot be opened. c002 a cannot close file an attempt to close the file failed. c003 a cannot read file an attempt to read the file failed. it is likely that the file has collapsed. c004 a cannot seek file an attempt to seek the file failed. c005 f illegal file type the format of the file is illegal. this file cannot be handled. c006 f illegal magic number the magic number for the load module file is illegal. c007 f this file is not load-module file the specified file is not a load module file. c008 f old coff version the version of the load module file is illegal. c009 a not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window. c00a f illegal address the address is illegal. c00b f lm not load the load module file has not been loaded. c00c f illegal argument this is an internal error. c00d f user program is emulating a user program is running. this command cannot be executed. c00e f user program is tracing the tracer is running. this command cannot be executed. c010 a communication failed communication with the ie is impossible. check whether the ie is abnormal. c011 f illegal file format the format of the load module file (lnk) is illegal. c012 f check sum error a checksum error occurred in reading the load module file. check the load module file. c013 f too big size the address range for uploading has exceeded 1m byte. c014 f cannot write file an attempt to write to the file failed. c100 f not support the tektronix format is not supported. d001 f not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window. e000 f illegal argument this is an internal error. e001 f illegal start address the start address is illegal. e002 f illegal end address the end address is illegal. e003 f size too long the address value is illegal. e004 f cant open file the specified file cannot be opened.
appendix a error messages 86 error messages (9/9) error no. type message explanation e005 f cant read file an attempt to read the file failed. it is likely that the file has collapsed. e006 f cant seek file an attempt to seek the file failed. e007 f cant write file an attempt to write to the file failed. e008 f not enough memory there is no sufficient memory. end unnecessary applications, or close the debugger window. e009 f illegal file format the format of the file is illegal. xxxx f internal error an internal error occurred.
appendix b key functions 87 appendix b key functions debugging can be carried out more effectively when ID78K0 is operated using the special function keys. in the following explanation of the special function keys, general key representations (generic key representations) are used. for the ibm-pc/at series, the key representations may differ slightly depending on the keyboard type. b.1 functions of special function keys key pc-9801 and 9821 series ibm-pc/at series function bs backspace deletes the character immediately before the cursor and moves the cursor to the position of the deleted character. the character string following the cursor is moved back. copy printscreen captures the entire screen into the clipboard as a bit image. (windows function) esc esc <1> closes the pulldown menu. <2> closes the modal dialog box. grph alt moves the cursor to the menu bar. help end displays the last line. also, the cursor is positioned to the last line. home clr home displays the first line. also, the cursor is positioned to the first line. roll up pageup scrolls the display up by one screen. also, the cursor is positioned to the top of the screen. roll down pagedown scrolls the display down by one screen. also, the cursor is positioned to the top of the screen. space space inserts one blank. tab ta b positions the cursor to the next item. - - moves the cursor up. scrolls the screen down by one line when the cursor is positioned to the top of the screen. moves the cursor down. scrolls the screen up by one line when the cursor is at the bottom of the screen. ? ? moves the cursor to the left. scrolls the screen to the right by one item when the cursor is in the leftmost column. ? ? moves the cursor to the right. scrolls the screen to the left by one item when the cursor is in the rightmost column. ? ? confirms input data.
appendix b key functions 88 b.2 functions of special function keys ( ctrl + key) key (common to the pc-9801, 9821, and ibm-pc/at series) function a using the data value in the current window as an address to jump to, disassembles and displays the program starting from that address. opens the assemble window. b sets a breakpoint in a selected line. c copies a selected character string to the clipboard buffer. d pc setting and window view: the call dialog box is opened. e pc setting. f switches a window to modify mode. this has the same effect as clicking the button. g executes a program. this has the same effect as clicking the button. h switches a window to the hold state. i switches a window to the active state. m using the data value in the current window as an address to jump to, displays the contents of memory starting from that address. opens the memory window. o if the source window is current: allows the user to select a source view file. opens the source file select dialog box. otherwise: displays an appropriate view file in the current window. opens the view file save dialog box. p stops the execution of a program. this has the same effect as clicking the button. r performs step execution until control returns to the calling function. this has the same effect as clicking the button. s saves the contents of the current window to a view file. t performs step execution. this has the same effect as clicking the button. u using the data value in the current window as an address to jump to, displays an appropriate source text and source line. opens the source window. v pastes the contents of the clipboard buffer to the text cursor position. w switches a window to view mode. this has the same effect as clicking the button. x performs next step execution. this has the same effect as clicking the button. z cancels the previous editing operation.
appendix c menus 89 appendix c menus this appendix lists the menus supported by ID78K0. symbols used in the menu lists symbol meaning [item] item on a menu bar no symbol item in a pull-down menu ? ? (arrow) item in a cascaded menu the number of arrows corresponds to the nesting level. table c-1 main window (1/4) menu mnemonic explanation [file] open... ctrl+o opens a file. save ctrl+s saves the contents of the current window into the view file. save as... saves the contents of the current window into a view file having a different name. close closes the current window. print prints the contents of the current window. down load... downloads a program. up load... uploads a program. open/save project ? open project... opens a project file. ? save overwrites the project file with the current debugging environment. ? save as... saves the current debugging environment into a project file. open/save log records the history of execution. exit exits from the debugger. [edit] undo ctrl+z cancels the most recent editing. copy ctrl+c copies a selected character string into the clipboard buffer. paste ctrl+v pastes the contents of the clipboard buffer at the point to which the text cursor is positioned. write in writes the modified contents into the target device. restore cancels the modified contents. memory ? memory fill... initializes memory. ? memory copy... copies the contents of memory. ? memory compare... compares the contents of memory. ? file compare... compares the view file with the contents of memory.
appendix c menus 90 table c-1 main window (2/4) menu mnemonic explanation [view] search... searches for a character string or numerical value. address... displays the contents of memory at a specified address. view variable... displays the value of a specified variable temporarily. watch variable... displays the value of a specified variable continuously. add variable... adds a variable to the variable window. sym to adr... converts symbols. delete deletes a specified value. bin selects binary display format. oct selects octal display format. dec selects decimal display format. hex selects hexadecimal display format. proper selects a default display format for each variable. event ? displays event information. memory ? nibble displays data in nibble format. ? byte displays data in byte format. ? word displays data in word format. ? long displays data in long format. ? ascii switches on or off ascii view mode. sfr ? address sort selects alphabetic display order or display in order of addresses. ? pick up displays only modified sfrs. ? attribute ?? show displays the attribute view area. ?? hide hides the attribute view area. ? compulsion read performs forced reading of a read-protected sfr. ? synchronize writes the modified sfrs to the target device. trace view ? trace view... selects the trace view contents. ? snap view... selects the snapshot trace view contents. ? normal title displays the trace frame titles. ? snap title displays the snapshot frame titles. ? all title displays all titles. ? open frame... specifies a view frame number. ? pick up... selects a view frame. coverage ? 1 byte displays data in 1-byte units. ? 64 byte displays data in 64-byte units.
appendix c menus 91 table c-1 main window (3/4) menu mnemonic explanation [option] tool bar displays or hides the tool bar. status bar displays or hides the status bar. button displays or hides the buttons in the window. source mode selects the source mode. instruction mode selects the instruction mode. configuration... sets the environment. source path... sets source path information. extended option... sets extended options. mask option... sets mask options. [execute] stop ctrl+p stops the execution of a program. go ctrl+g executes a program. return ctrl+r executes a program, step by step, until control is returned to the calling function. step ctrl+t executes a program step by step. next ctrl+x performs next step execution of a program. go & go repeatedly executes a program. go & come executes a program up to a specified address. slowmotion continues step-by-step execution. cpu reset & go resets the cpu before starting execution. cpu reset... resets the cpu. set bp ctrl+b sets a breakpoint. set pc ctrl+e sets the address in the program counter. call... ctrl+d sets pc in the specified address and moves. extsenceclip... sets external sense clip mode. trace cond. trace sets conditional tracing mode. machine all. trace sets machine cycle, all-tracing mode. event all. trace sets event cycle, all-tracing mode. trace full break breaks after full tracing. [operation] active ctrl+i puts the window in the active state. hold ctrl+h puts the window in the hold state. tomodify ctrl+f puts the window in modify mode. toview ctrl+w puts the window in view mode. window connect ? sourcetext links to the source window. ? assemble links to the assemble window. ? memory links to the memory window.
appendix c menus 92 table c-1 main window (4/4) menu mnemonic explanation [browse] sourcetext... opens the source window. variable... opens the variable window. assemble... opens the assemble window. memory... opens the memory window. register... opens the register window. stack trace... opens the stack window. sfr... opens the sfr window. local variable... opens the local variable window. breakset... opens the break dialog box. timer... opens the timer window. trace ? traceset... opens the trace dialog box. ? traceview... opens the trace view dialog box. ? snapshottraceset... opens the snap-shot dialog box. event ? eventset... opens the event set dialog box. ? eventmanager... opens the event manager. ? eventlinkset... opens the event link dialog box. coverage ? view... opens the coverage window. ? clear... opens the coverage memory clear dialog box. ? condition... opens the coverage condition setting dialog box. ? efficiency... opens the coverage efficiency view dialog box. [jump] sourcetext... ctrl+u jumps to the source window. assemble... ctrl+a jumps to the assemble window. memory... ctrl+m jumps to the memory window. [window] cascade displays the window in cascade style. tile displays the window in tile style. arrange icons re-arranges the icons. close all closes all windows except the main window. [help] about... displays the information about the version.
appendix c menus 93 table c-2 event manager menu mnemonic explanation [file] open... opens an event setting file. save saves the current event settings into the event setting file, overwriting the previously saved setting. save as... saves the current event settings into a specified event setting file. print prints the event registration/setting information. close closes the event manager. [edit] undo cancels the most recent editing. copy copies a specified icon using a different name. all select selects all icons. delete deletes a specified icon. [view] name sorts the icons into event name order. kind sorts the icons into event type order. detail switches between normal view and detail view. [execute] set break enables a break condition. cancel break disables a break condition. set trace enables a trace condition. cancel trace disables a trace condition. set snapshottrace enables a snapshot condition. cancel snapshottrace disables a snapshot condition. [operation] breakset... opens the break dialog box. traceset... opens the trace dialog box. snapshottraceset... opens the snap-shot dialog box. eventset... opens the event set dialog box. eventlinkset... opens the event link dialog box. [jump] sourcetext... jumps to the source window. assemble... jumps to the assemble window. memory... jumps to the memory window.
appendix c menus 94 table c-3 register window menu mnemonic explanation [file] open/save condition ? open condition... opens the selected file for reference. ? save condition saves the contents of the window into a view file. ? save file as... saves the current event settings into a specified view file. close closes the register window. [edit] undo cancels the most recent editing. copy copies a selected character string into the clipboard buffer. paste pastes the contents of the clipboard buffer at the point to which the text cursor is positioned. write in writes the modified contents into the target device. restore cancels the modified contents. [view] absolute name displays absolute register names. functional name displays functional register names. register displays registers individually. register pair displays register pairs. bin displays data in binary format. oct displays data in octal format. dec displays data in decimal format. hex displays data in hexadecimal format. [operation] active puts the register window in the active state. hold puts the register window in the hold state. tomodify puts the register window in modify mode. toview puts the register window in view mode. [jump] sourcetext... jumps to the source window. assemble... jumps to the assemble window. memory... jumps to the memory window.
appendix c menus 95 table c-4 variable window menu mnemonic explanation [file] open/save condition ? open condition... opens the selected file for reference. ? save condition saves the contents of the window into a view file. ? save file as... saves the contents of the window into a specified view file. close closes the variable window. [edit] undo cancels the most recent editing. copy copies a selected character string into the clipboard buffer. paste pastes the contents of the clipboard buffer at the point to which the text cursor is positioned. write in writes the modified contents into the target device. restore cancels the modified contents. [view] bin displays variable values in binary format. oct displays variable values in octal format. dec displays variable values in decimal format. hex displays variable values in hexadecimal format. proper displays variable values in default format for each variable. [operation] active puts the variable window in the active state. hold puts the variable window in the hold state. tomodify puts the variable window in modify mode. toview puts the variable window in view mode. delete removes a specified variable from the variable window. table c-5 timer window menu mnemonic explanation [file] open/save condition ? open condition... opens a file. ? save condition saves the contents of the window into the original file. ? save file as... saves the contents of the window into a specified file. close closes the timer window. [operation] active places the timer window in the active state. hold places the timer window in the hold state.

although nec has taken all possible steps to ensure that the documentation supplied to our customers is complete, bug free and up-to-date, we readily accept that errors may occur. despite all the care and precautions we've taken, you may encounter problems in the documentation. please complete this form whenever you'd like to report errors or suggest improvements to us. hong kong, philippines, oceania nec electronics hong kong ltd. fax: +852-2886-9022/9044 korea nec electronics hong kong ltd. seoul branch fax: 02-528-4411 taiwan nec electronics taiwan ltd. fax: 02-719-5951 address north america nec electronics inc. corporate communications dept. fax: 1-800-729-9288 1-408-588-6130 europe nec electronics (europe) gmbh technical documentation dept. fax: +49-211-6503-274 south america nec do brasil s.a. fax: +55-11-6465-6829 asian nations except philippines nec electronics singapore pte. ltd. fax: +65-250-3583 japan nec semiconductor technical hotline fax: 044-548-7900 i would like to report the following error/make the following suggestion: document title: document number: page number: thank you for your kind support. if possible, please fax the referenced page or drawing. excellent good acceptable poor document rating clarity technical accuracy organization cs 98.2 name company from: tel. fax facsimile message

▲Up To Search▲

Price & Availability of ID78K0

	To Download ID78K0 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .